I second this. I ran into this problem the other day. I didn't have
time to investigate it deeply and I had my pre-maven days build.xml
around so I used it instead.
maven.dependency.classpath seems to be setup in do-env, so it's pretty
early in the build process. But I am concerned that ant can't export
back 'up' a call tree. However, the callback's do provide a way to
call from 'below' the do-env. I am going to try that when I get a
chance.
Evan
On Tuesday 21 May 2002 08:40 am, James Strachan wrote:
> I just wondered if anyone had figured out how to do this in Maven
> yet. I tend to add a bunch of helper targets in build files to run
> certain sample programs or individual test cases. e.g. like this...
>
> <target name="demo.hw" depends="compile.test" description="Runs
> the Hello World demo">
> <java classname="org.apache.commons.jelly.Jelly" fork="yes">
> <classpath refid="test.classpath"/>
> <arg
> value="src/test/org/apache/commons/jelly/hello_world.jelly"/>
> </java>
> </target>
>
> What'd be really cool is if running the maven:compile task we could
> export the ${maven.dependency.classpath} so that it can be used by
> the project build.xml. I guess we could be constrained here with
> what Ant can support and whether it can output <path> variables
> from an inner Ant build to an outer one.
>
> James
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
