Best Regards Global Identity A/S, Jens Fournais CEO
Bygstubben 3 | DK-2950 Vedbaek | Denmark Phone: +45 45 99 31 | E-mail: [EMAIL PROTECTED] Please visit our website at: http://www.elibitum.com "Vincent Massol" <[EMAIL PROTECTED]> 07-07-2005 19:40 Please respond to "Maven Developers List" <dev@maven.apache.org> To "'Maven Developers List'" <dev@maven.apache.org> cc Subject RE: Mixed plugins and functional tests for plugins? (was RE: [m2] Clvoer plugin location (was RE: [m2] Forking a customlifecycle in a report plugin?)) > -----Original Message----- > From: Trygve Laugstøl [mailto:[EMAIL PROTECTED] > Sent: mercredi 6 juillet 2005 10:38 > To: Maven Developers List > Subject: Re: Mixed plugins and functional tests for plugins? (was RE: [m2] > Clvoer plugin location (was RE: [m2] Forking a customlifecycle in a report > plugin?)) [snip] > > > I still think it would make more sense to make these functional tests > > > normal JUnit tests and instead of having a tester plugin just have a > > > simple tool for embedding Maven 2 because you still need to do > assertions > > > after you've executed Maven. > > Got a opinion on this? Sure, that sounds good. The tester plugin was just meant to be a little wrapper around this idea. But I'm fine to start with your idea of this simple tool and take it from there. > > The tester plugin would not have any assertion itself (apart from the > > executing project failing). The tests are done by the executing plugin > and > > the verifier plugin can be used to perform high level assertions. > > Isn't the executing plugin the "real" plugin itself? Sorry, my fault. I meant "executing project" and not "executing plugin". -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
