My answer to my own question. I think it's not optimal since it puts *all* of
the platform JARs in the javadoc classpath. But it does the job.
Content of an Ant target to be put in the module suite build.xml.
<target name="javadoc-suite-build" depends="-init, -jdk-init">
<mkdir dir="${suite.build.dir}/javadoc/"/>
<javadoc destdir="${suite.build.dir}/javadoc/" useexternalfile="yes"
access="public" encoding="UTF-8" charset="UTF-8">
<sourcefiles>
<fileset dir="${basedir}">
<include name="**/src/**/*.java" />
</fileset>
</sourcefiles>
<classpath>
<fileset dir="${nbplatform.active.dir}" />
<fileset dir="${basedir}/build/cluster/modules/" />
</classpath>
</javadoc></target>
---------------
Le mardi 17 septembre 2019 à 22:33:28 UTC+2, Jerome Lelasseux
<lelass...@yahoo.com.INVALID> a écrit :
Using the IDE I can generate a javadoc project by project (module by module).
But how to do it on a module suite? Any help welcome.
I tried adding an Ant target for this (reusing part of the PraxisLive
build.xml) to do this but it does not work : I don't know how to get the
-classpath parameters for the Ant javadoc command, i.e. retrieve the list of NB
platform jars used by my code. I'm new to Ant and to the NB build harness...
