Ok, I guess I am just stupid. This isn't working. Yes, it echos a path, but
it doesn't seem to be using this path to launch ant.
<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>
<ant:ant dir="${basedir}" antfile="build.xml" target="all"/>
</goal>
Is ant going to use the $[base] as the launch classpath? That's what I want.
That's what we do now...
Or do I need to alter all my build files to read this property I've created
and create a class path...
-----Original Message-----
From: Maury Jarrell [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 26, 2004 4:44 PM
To: Maven Users List
Subject: Re: Pass classpath to ant
> 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
