Hello Roland & Edwin
I think I found the problem!
We have an empty super project with several modules/sub-projects. Now I
configured the antrun-plugin with <inherited>false</inherited> and
<phase>test-compile</phase> and expected it to run after all
sub-projects have compiled their test-sources. But that isn't the case!
The order is like this:
----------------------
'super project'
...
test-compile
ant-run
test
module1
...
test-compile
test
...
----------------------
We expected it to be:
----------------------
'super project'
test-compile
module1
test-compile
'super project'
ant-run
test
module1
test
...
----------------------
Hope this helps someone else someday, who has the same problem! We
solved the problem with configuring the antrun-plugin with
<inherited>true</inherited> and now the ant-script is called for every
sub-project.
Thanks anyway!
Bye, Thomas
Edwin Punzalan schrieb:
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
