Re: Javadoc build problems with JDK 1.5 code?

[Martin Zaun <Ma...@Sun.COM>]

Hi,
running 'ant javadoc' in the trunk aborts with jdk-1.5-related errors.
I was wondering if they've been worked on already, since there was an
old email thread and we decided to require JDK 1.5.

Also, I'd like to use the {@code ...} tag for easy quoting of verbatim
text in javadocs, which requires JDK 1.5.

To fix the javadoc errors, I simply had to increase the "vmlevel" value
to "1.5" under:  <target name="testing-javadoc-14" unless="jdk16">...

Comments?

Martin

Bryan Pendleton wrote:
> Bryan Pendleton wrote:
>>> If changing the source level to 1.5 fixes it for you, I suggest that we
>>> just cross our fingers and hope that no one vetos the JDK 5 vote (the
>>> polls close at 5 pm PDT today) and check in the fix tomorrow. :)
>>
>> This change appears to work for me. If no other opinions are voiced,
>> I'll make this change in a day or two.
> 
> I made this change last night. You now need a JDK 1.5 build environment
> in order to build the engine javadocs for the trunk.
> 
> thanks,
> 
> bryan
> 

Re: Javadoc build problems with JDK 1.5 code?

["Dag H. Wanvik" <Da...@Sun.COM>]

Martin Zaun <Ma...@Sun.COM> writes:

> Hi,
> running 'ant javadoc' in the trunk aborts with jdk-1.5-related errors.
> I was wondering if they've been worked on already, since there was an
> old email thread and we decided to require JDK 1.5.
>
> Also, I'd like to use the {@code ...} tag for easy quoting of verbatim
> text in javadocs, which requires JDK 1.5.
>
> To fix the javadoc errors, I simply had to increase the "vmlevel" value
> to "1.5" under:  <target name="testing-javadoc-14" unless="jdk16">...
>
> Comments?

I guess that's tantamount to having source which is at level 1.4 in
the code, but the corresponding javadocs are at level 1.5. Not sure it
is a problem, though. It does add some potential for confusion as to
the source level to the build.xml, so the change should be commented
well. It seems good to be able to use to @code tag:

http://java.sun.com/j2se/1.5.0/docs/guide/javadoc/whatsnew-1.5.0.html

I did the javadoc build on my machine with this change and it
seemed to work.

But I am not familiar enough with the build system to vouch for its
safety.

Dag