On Thu, May 16, 2002 at 02:53:02AM -0400, Peter Meggitt wrote:
> I would like to be able to run a java application from within my
> build.xml. I would like to do this after maven sets the classpath and
> runs through its checks. What is the recommended way to do this? I
> added a post-env callback to run this as a maven:env callback. This
> seems to work but I'm wondering if there is a better way to accomplish
> this.
You can use the callback as you have; however, if you feel that you were
"forced" to use a callback simply to get access to the classpath, I'd be
interested in hearing about the target you created and what it does and
why it doesn't really fit in as a callback. The reason I am asking
these questions is that we are contemplating a patch that will enable
the maven properties and classpath to be available in the user's
top-level build file. This would not require you to use a callback to
execute your target.
> Actually I did have to make a change to
> ${maven.home}/plugins/core/build.xml to get this to work. Everywhere
> where a callback is made the property maven.base.classpath is set:
> <property name="maven.build.classpath" value="classpath"/>. I changed
> "classpath" to "${maven.dependency.classpath}". Also I keep getting a
> message about updating my project file: "ERROR: The specified update
> can not be performed, please check your maven.toVersion and
> maven.fromVersion and try again." How can I get rid of this? P.S. I
> took a CVS copy about 11pm EST 05-15-02.
This has been corrected recently. The path references are now correctly
passed to the callbacks.
Thanks!
Pete
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
