Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: pass (asf.osuosl.org: domain of simon.willnauer@googlemail.com
 designates 66.249.92.169 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=googlemail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references;
        b=mqCfTm1xnEtzpz4JpHDGUvpB5cdqKETdC/c7ho5530i1viqfQ+KHo4WnZCCkf30qbNFg+2RC6I2QDhYkhO7Gz88QkYgzR2BFdo9rmXPjI6JLl1b7o5imwJ6d2yJ6xF7ExFGG+TVUh3mnCZyIog4ejTmc4knAOlozpw9KEQIGdDY=
Message-ID: <f18c9dde0606141451p1adfdeb9o20ea6776de93f3fd@mail.gmail.com>
Date: Wed, 14 Jun 2006 23:51:49 +0200
From: "Simon Willnauer" <simon.willnauer@googlemail.com>
Reply-To: simon.willnauer@gmail.com
To: "Chris Hostetter" <hossman_lucene@fucit.org>, java-dev@lucene.apache.org
Subject: Re: javadoc compilation problem?
In-Reply-To: <Pine.LNX.4.58.0606141154410.24006@hal.rescomp.berkeley.edu>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_14508_18971026.1150321909728"
References: 
 <OF29E36167.85A6C707-ONC225718D.00520425-C225718D.005293D0@il.ibm.com>
	 <f18c9dde0606140941x35308903w52f7d8116fb2ccdb@mail.gmail.com>
	 <Pine.LNX.4.58.0606141154410.24006@hal.rescomp.berkeley.edu>

------=_Part_14508_18971026.1150321909728
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I had a similar approach to this working on 1.4 but you have been 5 min
faster ;)
Never mind... I tried yours on java 1.4.2_12 (windows) and blackdown
1.4(linux) it is working fine for my
1.4 JVM's
but I do agree with you that we need a better way to deal with 1.5 dependent
contib modules. Me and Doug didn't try the javadoc task before committing
this. ;( bad idea!

Simon

On 6/14/06, Chris Hostetter <hossman_lucene@fucit.org> wrote:
>
>
> : I tried building the java doc without any errors using java  5 but
> : using 1.4the api doc can not be build.
>
> the problem is that javadoc has to parse the files to generate the docs,
> and the 1.4 javadoc binary doesn't understand the 1.5 syntax.
>
> I've just commited a change to the build.xml so that it will only attempt
> to do the GData javadocs if it detecs that the users is running in a 1.5
> JVM.  If a few people could try this out on both 1.4 and 1.5 and sanity
> check it for me i'd appreciate it (i did test it, but it's always good to
> get a few eye balls)
>
> I feel it's important to point out, the way i did this feels like a big
> freaking hack to me ... if we want to support 1.5 contrib modules moving
> forward, we're going to want a more reobust way to deal with this.
>
>
> -Hoss
>
>

------=_Part_14508_18971026.1150321909728--