> -----Original Message----- > From: Rafal Krzewski [mailto:[EMAIL PROTECTED] > Sent: Friday, February 06, 2004 10:51 AM > To: Maven Developers List > Subject: Re: RC2 > > > [EMAIL PROTECTED] wrote: > > Maczka Michal <[EMAIL PROTECTED]> wrote on 05/02/2004 > 09:59:36 PM: > > > >>For example if cactus test cases were kept in separate, dedicated > > > > project > > > >>this particular problem will almost disappear. > > > > > > We do exactly this at the moment for our J2EE apps. > > I should probably read the docs and all, but... > > Is it possible to get Clover reports for Cactus tests? And what if the > tested code comes from another maven project? > > R. >
I agree with dIon that some things are alredy are usable, but what I was trying to say is: The level of integration between plugins for doing functional testing (aka integration testing) is very poor. But this is quite common problem in Maven. This has nothing to do with Maven core or our bugs. It is rather a question of lack of common guidelines which will demonstrate how to use such tools and generally how to write a plugin from given category (e.g from categtory "code generators" "ui testing") This situation is natural and was inevitable as many ideas were growing up with maven. Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
