I just wanted it to be easier to see the purpose from the outside
instead of globbing them all together.
On 27 Oct 07, at 6:58 PM 27 Oct 07, Brian E. Fox wrote:
If you look here:
https://svn.apache.org/repos/asf/maven/core-integration-testing/trunk/co
re-integration-testing-plugins
You will notice that we seem to have separate whole plugins for
individual purposes. Is there a reason that each one needs to be a
separate plugin as opposed to a new mojo in a single plugin? Having
one
seems like it would be easier to manage and possibly quicker to
execute
since it would only need to be resolved and downloaded once (unless
cleared by an it).
Assuming that at least some of these can be combined, and since I
need a
new mojo and there isn't an obvious place to add one, I'm going to
create a maven-it-plugin-all. Unless there's a good reason, this
should
be used for future tests instead of making a new one.
--Brian
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
