If the surefire plugin (and compiler plugin) and such were more
configurable, so you wouldn't have to sub-class them to make plugins
for integration tests, then the simple mode would be to bind them at
other phases to compile and execute tests in those phases. That would
be nice.
Christian.
On 6-Aug-08, at 18:00 , John Casey wrote:
Mainly, it's useful for testing various POM configurations, both for
the core and for maven plugins. Outside of that, I don't imagine
you'd want to use it, except possibly to spawn sub-builds for
something exotic.
-john
Paul Benedict wrote:
I work in a team that heavily writes unit and integration tests.
Typically, our unit tests end in *Test and our integration tests end
in *ITest (*HibernateITest, *MailITest, etc.). We put integration
tests into a profile so they run only when requested.
So I've been reading the Invoker documentation and it claims it is
useful. Why is it useful? I don't understand what the purpose of
creating separate projects for integration testing. I understand how
that's useful for Maven's own integration testing (gotta test project
configs), but how for the rest of Java developers? Can someone
expound
upon it? Is it just a preference? Is there an actual purpose?
Thanks,
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
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]
