Return-Path: Delivered-To: apmail-buildr-users-archive@www.apache.org Received: (qmail 91031 invoked from network); 15 Nov 2010 21:40:52 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 15 Nov 2010 21:40:52 -0000 Received: (qmail 94683 invoked by uid 500); 15 Nov 2010 21:41:23 -0000 Delivered-To: apmail-buildr-users-archive@buildr.apache.org Received: (qmail 94657 invoked by uid 500); 15 Nov 2010 21:41:23 -0000 Mailing-List: contact users-help@buildr.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@buildr.apache.org Delivered-To: mailing list users@buildr.apache.org Delivered-To: moderator for users@buildr.apache.org Received: (qmail 12388 invoked by uid 99); 15 Nov 2010 20:59:31 -0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of simon.harrer@gmail.com designates 209.85.214.172 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=NjUCwhpEW1pRl2+NjppN/mTqk3lJp05g0EuctHiLFOA=; b=kEJ4I8ns+yH0heWmCiWNfK0IS05u1Um7Xea7z/YHAjNSErSWhb6hRI1YBojTq+uZ5D x6hYsdI++lNg4NMdaMA7iKhASWTk9CIbD0OGdQ6ZeVuQ/YdiQFEZBKuu+hEporcv7Rz+ I7q597H4quWUzCGu0Tr//WGXbnVdZPSvtZUPk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=YToGLWkkczmiglEOZ+FBpjVZdqqAEKwT9GWc/BgL2u/GjKaENQLIbgPBbX1GBqi9TX HJ9Nuu4fqa6WAVune54rkbqfe6xXcj/C/8poZT1PMMHg8dP2bYXCx2v9yay6f3SAGDPK K0hdp4fsHLjNsuNQD2dyRzKfb1FvXaaUFrhD8= MIME-Version: 1.0 In-Reply-To: References: From: Simon Harrer Date: Mon, 15 Nov 2010 21:58:36 +0100 Message-ID: Subject: Re: Building JavaDoc for Groovy Project To: users@buildr.apache.org Content-Type: multipart/alternative; boundary=000325574c3ea9bcdc04951db533 X-Virus-Checked: Checked by ClamAV on apache.org --000325574c3ea9bcdc04951db533 Content-Type: text/plain; charset=UTF-8 Hi, thanks for the comments. I found that groovydoc should do the job. And in the buildr documentation, it states, that groovydoc can be used. However, I could not get it to work. I searched in the sources and found no Doc Classes in the groovy folders. See http://buildr.apache.org/languages.html#groovy for reference to the groovydoc task My idea is to be able to use groovydoc only and produce a groovydoc for all of my projects which is combined like the javadoc is. Cheers, Simon On 11 November 2010 20:04, Simon Harrer wrote: > Hi buildr Community. > > I think buildr is really cool. But currently, I am stuck generating javadoc > > project structure: > src/main/java <-- java and groovy sources > target/classes <-- output folder > > This works perfectly with the groovyc joint compiler. > > However, when using the doc command, buildr states that it cannot guess the > language and aborts. And I do not find a way to specify that I want javadoc > generated for src/main/java. > > My only other solution would be to create such a javadoc task myself by > leveraging ant or the command line. Or is there a solution with buildr? > > Best regards, > Simon > --000325574c3ea9bcdc04951db533--