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 - 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. Does this sound ok? - Brett Vincent Massol wrote: > >> -----Original Message----- >> From: Brett Porter [mailto:[EMAIL PROTECTED] >> Sent: mercredi 25 janvier 2006 00:38 >> To: Maven Developers List >> Subject: Re: [PROPOSAL] Integration testing proposal for Maven 2.0.x >> >> +1 for src/it >> >> I've got to say I'm greatly hesitant to add new things to 2.0.3, but it >> wouldn't be the first time. Be careful :) >> >> How sure are we that this will be the final solution - are new test >> types needed? > > We're not sure at all! :-) I would even say that it's pretty sure that over > time the design and implementation solution will change. Which is why I > think it's good for the 2.0.x series: we're not changing any existing user > interface (only adding to them) and we're following the same spirit as the > current strategy for unit tests. > > It's possible that we'll need to change that in Maven 2.1.x series but the > best way to know is to implement what I suggest in 2.0.3 and get feedback. > >> Just trying to get a grip on where we are at with the topic as a whole. > > Thanks. > -Vincent > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
