You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Rick Hillegas <Ri...@Sun.COM> on 2006/04/14 16:32:23 UTC

jdk16 javadoc tool now usable on Derby

I have checked in a change to the way that we generate javadoc: If 
ant.properties points at a jdk16 installation, then we use the jdk16 
javadoc tool and include JDBC4 support classes in derbydocs and in the 
published api. If ant.properties does not point at a jdk16 installation, 
then we use the javadoc tool in $JAVA_HOME and we exclude the JDBC4 
support classes.

Please let me know if you have problems generating javadoc.

Thanks,
-Rick

Re: jdk16 javadoc tool now usable on Derby

Posted by Rick Hillegas <Ri...@Sun.COM>.
Thanks, Andrew!

Andrew McIntyre wrote:

>On 4/14/06, Rick Hillegas <Ri...@sun.com> wrote:
>  
>
>>I have checked in a change to the way that we generate javadoc: If
>>ant.properties points at a jdk16 installation, then we use the jdk16
>>javadoc tool and include JDBC4 support classes in derbydocs and in the
>>published api. If ant.properties does not point at a jdk16 installation,
>>then we use the javadoc tool in $JAVA_HOME and we exclude the JDBC4
>>support classes.
>>
>>Please let me know if you have problems generating javadoc.
>>    
>>
>
>Can't build the 1.4 javadoc on OS X now. Unlike Windows, JAVA_HOME
>corresponds to the top-level of the jdk installation. It's kind of
>weird to set JAVA_HOME to, say c:/andrew/jdk142 on Windows and have
>java.home come out being c:/andrew/jdk142/jre in the JVM. *shrug*
>
>I'll take care of it. I assume I can also remove the 'dummy' target
>while I'm in there? :-)
>
>andrew
>  
>

Re: jdk16 javadoc tool now usable on Derby

Posted by Andrew McIntyre <mc...@gmail.com>.
On 4/14/06, Rick Hillegas <Ri...@sun.com> wrote:
> I have checked in a change to the way that we generate javadoc: If
> ant.properties points at a jdk16 installation, then we use the jdk16
> javadoc tool and include JDBC4 support classes in derbydocs and in the
> published api. If ant.properties does not point at a jdk16 installation,
> then we use the javadoc tool in $JAVA_HOME and we exclude the JDBC4
> support classes.
>
> Please let me know if you have problems generating javadoc.

Can't build the 1.4 javadoc on OS X now. Unlike Windows, JAVA_HOME
corresponds to the top-level of the jdk installation. It's kind of
weird to set JAVA_HOME to, say c:/andrew/jdk142 on Windows and have
java.home come out being c:/andrew/jdk142/jre in the JVM. *shrug*

I'll take care of it. I assume I can also remove the 'dummy' target
while I'm in there? :-)

andrew