I'm intrigued by this patch, but am concerned about the overlap with
callbacks (I want to be sure we encourage the best approach). I
discussed this with Pete a bit on IRC this morning and he explained to
me that the problem with callbacks is that references were not being
passed. I made a small change (using out back-ported Ant task when
invoking callbacks) which seems to clear up that issue.
Thus what you were trying to accomplish in your original example --
invoking this target after compile:
<target name="hello.world">
<java classname="org.apache.foo.Bar" fork="yes">
<classpath>
<pathelement path="${maven.build.dest}"/>
<path refid="maven.dependency.classpath"/>
</classpath>
</java>
</target>
can be accomplished by adding this to project.properties:
maven.core.callback.post-compile.buildFile = build.xml
maven.core.callback.post-compile.buildTarget = hello.world
One of the nice things about this is that it does not require you to add
the special maven ant task to your projects local build file.
How do you feel about this approach?
-- jt
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>