> -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: jeudi 26 janvier 2006 22:14 > To: Maven Developers List > Subject: Re: [PROPOSAL] Integration testing proposal for Maven 2.0.x > > Vincent, > > There's a huge difference. Anything that goes into 2.0.3 must be made > compatible. If it lands on trunk we can have a longer testing period and > get people involved, and completely change it if it doesn't work out. > > I have the following concerns: > - adding an "it" scope. I haven't seen explained how this will behave, > nor the impact on existing plugins. > - adding something to the POM. I'm not sure the code is equipped to deal > with an upgraded POM version yet. It's something we were aware needed to > be done for 2.1. > - Are we still adding another set of tests (something formerly called > functional), or is it just two levels? > > Here's what I propose: > - formalise this in the wiki, cover as much as possible
I've just updated http://docs.codehaus.org/display/MAVEN/best+practices+-+testing+strategies Let me know if you have questions about what's there. > - when it comes to implementation, do it on trunk. Keep track of the > revisions and once we are 100% happy with it there, backport it to 2.0.3 > and confirm it is stable there. I'd love to do it but I've realized I still have lots of work on the m2 book's chapter. We need to decide where I spend my time and if someone can help. Let's discuss this offline. Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
