Return-Path: Delivered-To: apmail-incubator-buildr-user-archive@locus.apache.org Received: (qmail 95274 invoked from network); 12 Sep 2008 17:37:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Sep 2008 17:37:45 -0000 Received: (qmail 77936 invoked by uid 500); 12 Sep 2008 17:37:42 -0000 Delivered-To: apmail-incubator-buildr-user-archive@incubator.apache.org Received: (qmail 77906 invoked by uid 500); 12 Sep 2008 17:37:42 -0000 Mailing-List: contact buildr-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: buildr-user@incubator.apache.org Delivered-To: mailing list buildr-user@incubator.apache.org Received: (qmail 77854 invoked by uid 99); 12 Sep 2008 17:37:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Sep 2008 10:37:42 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of vic.borja@gmail.com designates 209.85.198.248 as permitted sender) Received: from [209.85.198.248] (HELO rv-out-0708.google.com) (209.85.198.248) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Sep 2008 17:36:44 +0000 Received: by rv-out-0708.google.com with SMTP id k29so922862rvb.0 for ; Fri, 12 Sep 2008 10:37:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=HYQe09EqP+DFftkb5lg8WRnLi/9eBuxPwf3RkSzU+2E=; b=vriU4rRTHyJbM0cwJ0P9crXEvkskMNYBpSZrseJcawRb78V5Xo9iuKcGbzsUEuBgT1 DHEDJl1VaY+VFTHi1fcPH2FoYzJDsKyUvOHUmeVWlpj97CpKYRtGNewHk+mZlmKFOtaZ JLS5JT61A2s+TFXeqRYBfgAE555zWHDaafW2I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=U89MpyBXPaWRiTx3mJWQ3s4JWUz9JLDqhVfbuGL+6WXzWk3vZwBMWHSBTSs4Z/GIEf dkCs00W1OEv+CYrhtFfNmXxoGoZy7JVjtfHvKfewiyudiUlNsMyUaTwsvPzMYHyD0XF8 q8UaGxJp1dTX1uGbw4LlYxVnH7sg3zavaK+fY= Received: by 10.140.193.16 with SMTP id q16mr2790920rvf.109.1221241026732; Fri, 12 Sep 2008 10:37:06 -0700 (PDT) Received: by 10.141.155.20 with HTTP; Fri, 12 Sep 2008 10:37:06 -0700 (PDT) Message-ID: <53466cf0809121037y7cde3991g2c18280da5d87bb4@mail.gmail.com> Date: Fri, 12 Sep 2008 12:37:06 -0500 From: "Victor Hugo Borja" To: buildr-user@incubator.apache.org Subject: Re: javadoc In-Reply-To: <3de5d7d20809121015l340fffm95d917850e8b8d4b@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_30381_13287878.1221241026715" References: <6539b1ea0809112257r35066654p8cf23a365b9bb75@mail.gmail.com> <3de5d7d20809120955q59c43af9if76dbfaf033acb5@mail.gmail.com> <53466cf0809121000l6f29e95dl263deefad6efa1b3@mail.gmail.com> <3de5d7d20809121015l340fffm95d917850e8b8d4b@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_30381_13287878.1221241026715 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I see..., and what you comment makes sense. So in order to generate javadoc for some projects all in the same target directory: define 'foo' define 'bar-api' do # just interfaces end define 'bar-impl' do # the impl, private classes, etc end define 'baz' do # another project end javadoc projects('bar_api', 'baz') end # buildr javadoc On Fri, Sep 12, 2008 at 12:15 PM, Assaf Arkin wrote: > On Fri, Sep 12, 2008 at 10:00 AM, Victor Hugo Borja > wrote: > > I think some users may expect the javadoc task to be recursive just like > > compile task, so that executing > > > > > buildr javadoc > > > > would generate javadoc for all projects defined. > > > > Should it be made recursive? If so, all it takes is adding > > project.recursive_task('javadoc') at java/compilers.rb:363 > > We can add that, but result is that it will recursively run all the > javadoc tasks which will recursively do nothing interesting. > > Javadoc tasks by default don't do anything, you need to tell each task > which source directories it should operate on. The reason for that: > if the default behavior was for javadoc to run with the same paths as > compile.sources, and run recursively, you will get a lot of javadoc > output directories (one per project). That's not what people want. > Most often, it's consolidated output from several different sources > (typically just the APIs), that way you get the package list, indexes, > cross reference working across the entire documentation. > > To accommodate for that, javadoc expects that you'll tell it exactly > which sources you want to document (typically projects), and you only > need one task to do that. > > Assaf > > > > > > > On Fri, Sep 12, 2008 at 11:55 AM, Assaf Arkin wrote: > > > >> On Thu, Sep 11, 2008 at 10:57 PM, Nicolas Modrzyk > >> wrote: > >> > Hi List, > >> > > >> > I was trying to generate the javadoc for the whole set of projects, > >> > where all the projects are children of a single parent project. > >> > Typing > >> > buildr javadoc > >> > at the root of the parent project, did not create anything: > >> > > >> > ======================================== > >> > (~/projects/tempo53)>buildr javadoc > >> > (in /Users/niko/projects/tempo53, development) > >> > Completed in 1.352s > >> > ======================================== > >> > > >> > What would be the proper way to get the javadoc for all the projects > >> > aggregated in the same place ? > >> > >> javadoc projects('foo', 'bar', etc) > >> > >> http://incubator.apache.org/buildr/rdoc/classes/Buildr/Javadoc.html > >> > >> > > >> > Niko, > >> > > >> > > > > > > > > -- > > vic > > > > Quaerendo invenietis. > > > -- vic Quaerendo invenietis. ------=_Part_30381_13287878.1221241026715--