2009/12/29 Brett Porter <[email protected]> > > On 29/12/2009, at 11:27 PM, Stephen Connolly wrote: > > > Any body got any objections / additional test cases to add? > > What about testing with Maven 2.2.1? Maybe even Maven 2.0.8 since they'll > get autoupgraded (yah, I know it's an old version). > > 1. if the pom is following best practice, it will have locked down the compiler version so we'd have to modify source code to rebuild the same project with the new m-compiler-p. This is what maven plugin enforcer does, it uses hooks in m3 that allow us to modify the project model in memory before the execution starts, which allows us to forcer the m-compiler-p to the new version.
2. Our plan is to make m-compiler-p require maven 2.0.9, so that nobody will be auto-upgraded. > > P.S. we should re-use this test plan for surefire > > I took a look and very little has changed in SVN since the last release so > this is pretty good to go. Further changes could certainly use it - though > it's also in the better position of having a stack of it's own ITs. > > Are we sure that the toolchains stuff has made it into surefire 2.5-SNAPSHOT yet? I suspect that the use case of running unit tests with a different toolchain from compiler has not been addressed, and I would like to add that in (but we can wait for 2.6 if we need too) I'd rather push the plugins out if we can, rather than holding on for fear of side-effects... this test plan is just a way of reducing the fear > - Brett > > -- > Brett Porter > [email protected] > http://brettporter.wordpress.com/ > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
