>> 2) Is the only way to add libraries to the build CLASSPATH to add a
>> dependency?
>
>Can you explain what you're trying to do? The dependencies listed in the
>project.xml file are available as ${maven.dependendency.classpath} which
>is a path references. Look at the java:jar goal to see how it is used.
>
I have a fairly complex set of build.xml files with sub-projects, etc. that
I'm trying to avoid replacing entirely. The source package includes multiple
directories with libraries that I'd like to be part of that
${maven.dependency.classpath}. If I have to put them in the repository and
define dependencies, I will, but I was looking for a way to use the existing
paths first.
--kd
==============================================================================
This e-mail is intended only for the use of the addressees. Any copying, forwarding,
printing or other use of this e-mail by persons other than the addressees is not
authorized. This e-mail may contain information that is privileged, confidential and
exempt from disclosure. If you are not the intended recipient, please notify us
immediately by return e-mail (including the original message in your reply) and then
delete and discard all copies of the e-mail. Thank you.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
