> Well, that builds an ant file with all the classpath dependencies built into
> the file. This isn't really what I want. I've got some pretty complex ant
> files. Initally, the big gain for us would be able to get rid of each
> project's jars and replace them with maven project.xml files defining
> dependecies.
>
Sorry, I'll read the question a little better next time. Try the
following. It just worked for me:
<goal name="testme">
<a:echo>This is a message.</a:echo>
<a:echo>${maven.junit.fork}</a:echo>
<a:path id="base.path">
<a:pathelement path="${pom.dependencyClasspath}"/>
<a:pathelement location="src"/>
</a:path>
<a:property name="base" refid="base.path"/>
<a:echo>${base}</a:echo>
</goal>
The variable $pom.dependencyClasspath accesses the
maven.dependency.classpath. The tasks after show how to echo it.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
