db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <Richard.Hille...@Sun.COM>
Subject Re: [jira] Assigned: (DERBY-1079) Build javadoc under jdk 1.6
Date Wed, 12 Apr 2006 18:08:04 GMT
Thanks, Andrew. I will play around with this. I may try something more 
elaborate too:

o Use the jdk16 javadoc if ant.properties points to a 1.6 installation
o Don't exclude the jdbc40 classes from the javadoc at all. If 
ant.properties doesn't point at a 1.6 intallation, then they won't be 
built anyway.

Cheers,
-Rick

Andrew McIntyre wrote:

>On 4/12/06, Rick Hillegas (JIRA) <derby-dev@db.apache.org> wrote:
>  
>
>>     [ http://issues.apache.org/jira/browse/DERBY-1079?page=all ]
>>
>>Rick Hillegas reassigned DERBY-1079:
>>------------------------------------
>>
>>    Assign To: Rick Hillegas
>>    
>>
>
>Thought about this the other day. One way to go would be to add an
>executable attribute to the publishedapi's <javadoc> task, and
>parameterize the includesfile part. Then, create a new includesfile
>that contains the jdk16 classes, and then have a couple of new
>targets:
>
><target="publishedapi" depends="publishedapi.jdk14,publishedapi.jdk16"/>
>
><target="publishedapi.jdk14">
>  <antcall target="do.publishedapi" unless="jdk16">
>    <param name="publishedapi.executable" value="${java.home}/bin/javadoc"/>
>    <param name="publishedapi.includesfile"
>value="${javadoctools.dir}/publishedapi.ant"/>
>  </antcall>
></target>
>
><target="publishedapi.jdk16" if="jdk16">
>  <antcall target="do.publishedapi" unless="jdk16">
>    <param name="publishedapi.executable" value="${jdk16}/bin/javadoc"/>
>    <param name="publishedapi.includesfile"
>value="${javadoctools.dir}/publishedapi16.ant"/>
>  </antcall>
></target>
>
><target name="do.publishedapi">
>  ... old target, paramterized, goes here ...
></target>
>
>andrew
>  
>


Mime
View raw message