Generating javadocs for fop ant task
I am having trouble automating an error free build of the javadocs
target in our build.xml. The problem is that I am using a RPM install
for ant (obviously I am talking Linux here). This places the ant.jar
file not into ${ant.home}/lib but into /usr/share/java. This means the
pathelement location=${env.ANT_HOME}/lib/ant.jar/ line in build.xml
will not find the ant.jar file.
Obviously ant.jar will be in the classpath as we are running ant at the
time. Any ideas how to get the ant.jar location from the ant invocation
classpath into the pathelement above?
Thanks
Manuel
Re: Generating javadocs for fop ant task
On Thu, 27 Oct 2005 03:03 pm, Mark C. Allman wrote:
Since you're using Linux, try a symbolic link (ln -s
/usr/share/java/ant.jar $ANT_HOME/lib/ant.jar )?
Mark, yes sure but that's not quite what I am after. The problem I want
to solve is to have a build.xml such that when users download the FOP
source distribution it will build without errors. To achieve that
build.xml must be able to find out where ant.jar lives for the javadocs
target. The current setup is broken for users who have ant installed
via RPM.
Manuel
-- Mark C. Allman
-- Allman Professional Consulting, Inc.
-- www.allmanpc.com http://www.allmanpc.com , 617-947-4263
BusinessMsg -- the secure, managed, 100% J2EE Enterprise IM plug-in
solution.
On Thu, 2005-10-27 at 18:46 +0800, Manuel Mall wrote:
I am having trouble automating an error free build of the javadocs
target in our build.xml. The problem is that I am using a RPM install
for ant (obviously I am talking Linux here). This places the ant.jar
file not into ${ant.home}/lib but into /usr/share/java. This means
the
pathelement location=${env.ANT_HOME}/lib/ant.jar/ line in
build.xml
will not find the ant.jar file.
Obviously ant.jar will be in the classpath as we are running ant at
the
time. Any ideas how to get the ant.jar location from the ant
invocation
classpath into the pathelement above?
Thanks
Manuel
Re: Generating javadocs for fop ant task
As I typed my last e-mail, I suspected that wasn't what you were looking for (it's trivial!).
Have you tried just adding the classpath as a pathelement instead of explicitly setting individual jars? I.e.,
pathelement path=${env.CLASSPATH} /
instead of
pathelement location=${env.ANT_HOME}/lib/ant.jar /
-- Mark C. Allman
-- Allman Professional Consulting, Inc.
-- www.allmanpc.com, 617-947-4263
BusinessMsg -- the secure, managed, 100% J2EE Enterprise IM plug-in solution.
On Thu, 2005-10-27 at 19:21 +0800, Manuel Mall wrote:
On Thu, 27 Oct 2005 03:03 pm, Mark C. Allman wrote:
Since you're using Linux, try a symbolic link (ln -s
/usr/share/java/ant.jar $ANT_HOME/lib/ant.jar )?
Mark, yes sure but that's not quite what I am after. The problem I want
to solve is to have a build.xml such that when users download the FOP
source distribution it will build without errors. To achieve that
build.xml must be able to find out where ant.jar lives for the javadocs
target. The current setup is broken for users who have ant installed
via RPM.
Manuel
-- Mark C. Allman
-- Allman Professional Consulting, Inc.
-- www.allmanpc.com http://www.allmanpc.com , 617-947-4263
BusinessMsg -- the secure, managed, 100% J2EE Enterprise IM plug-in
solution.
On Thu, 2005-10-27 at 18:46 +0800, Manuel Mall wrote:
I am having trouble automating an error free build of the javadocs
target in our build.xml. The problem is that I am using a RPM install
for ant (obviously I am talking Linux here). This places the ant.jar
file not into ${ant.home}/lib but into /usr/share/java. This means
the
pathelement location=${env.ANT_HOME}/lib/ant.jar/ line in
build.xml
will not find the ant.jar file.
Obviously ant.jar will be in the classpath as we are running ant at
the
time. Any ideas how to get the ant.jar location from the ant
invocation
classpath into the pathelement above?
Thanks
Manuel
signature.asc
Description: This is a digitally signed message part
