On Tue, 2004-05-18 at 05:09, Arnaud Heritier wrote:
> Yes, sorry, the log isn't correct.
> The problem was that you couldn't call "ant javadoc" direclty because we
> used this classpath
>
> <classpath>
> <fileset dir="$${libdir}">
> <include name="*.jar"/>
> </fileset>
> <pathelement location="$${defaulttargetdir}/$${final.name}.jar"/>
> </classpath>
>
> $${defaulttargetdir}/$${final.name}.jar is created in the jar target.
so is it a classpath problem or a goal dependency one?
It seems like this jar is not needed tfor resolution. The sourcepath is
defined, and only the libraries are needed in the path.
You should probably remove the ...{final.name}.jar path element and the
introduced goal dependency.
I checked in one of my projects and I only use the build.classpath for
the javadoc task.
<path id="build.classpath">
<fileset dir="${lib.dir}" >
<include name="**/*.jar"/>
</fileset>
</path>
<path id="run.classpath">
<pathelement path="${classes.dir}"/>
<path refid="build.classpath" />
</path>
[..]
<javadoc packagenames="${packages}"
destdir="${javadocs.dir}"
author="true"
version="true"
use="true"
windowtitle="${project.name} ${project.version}"
doctitle="${project.name} ${project.version}<br> API"
bottom="${copyright}"
source="1.4">
<classpath refid="build.classpath" />
[...]
Maybe could we use classpath references in that jelly file? At least for
the build.classpath one. It is used 4 times in the file (1.0.rc2).
Jerome
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
