Roland is right. You can bind your plugin to the test-compile phase,
and your plugin will run LAST during the test-compile phase. So it
would look like your running the plugin after the other test-compile
plugins yet its before the test phase.
^_^
Roland Asmann wrote:
Hi Thomas,
Every plugin you 'attach' to a certain phase, gets run AFTER the default
plugins for that phase are run.
If you want multiple plugins to run, the order of defining them is the order in
which they run (respecting
the default as the very first to run).
In your case, I suggest you attach your plugin to the 'test-compile'-phase,
since you already said
yourself you want it to run AFTER compiling, but BEFORE testing...
And forget about writing your own plugins, just stick with antrun, it'll do the
trick for you!
Roland
On Thursday 08 June 2006 09:59, Thomas Marti wrote:
Hallo Edwin
Thanks for you response. We want to run an ANT-Script with the
maven-antrun-plugin. Which <phase> do we have to specify in the
<execution>-tag, so that it runs after test-compile, but before the
tests are run??
Thanks and bye,
Thomas
Edwin Punzalan schrieb:
What is your use case?
If your plugin needs to run after the test phase but you don't want to
run the package phase, then you can fork the lifecycle and use:
@execute phase="test"
for more info, please see:
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle
.html
Hope that helps.
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
