This is totally different than changing the version of xx-maven-plugin used by the ITs. I appreciate testing with a new version of JUnit, or whatever. That is totally different than changing the version of a maven plugin used by an IT.
Don't mess with existing tests. It's always wrong to do it. You're lazy and stupid if you do it. On Sun, Feb 9, 2014 at 11:14 PM, Igor Fedorenko <[email protected]> wrote: > I successfully used junit4 parametrized tests with Invoker to run plugin > ITs against multiple versions of Maven. Didn't really need to do > anything special, everything just worked. The only minor inconvenience > was, IIRC, I had to use system properties to tell Invoker maven home. > Should be trivial to fix. > > -- > Regards, > Igor > > > On 2/9/2014, 23:00, Mark Derricutt wrote: >> >> Is it feasible to somehow change the IT test infrastructure to run >> against multiple versions? So that the best of both worlds is available >> ( at the expense of longer build times ). >> >> Thats one thing I'd love to have with the invoker plugin ( not sure if >> these IT tests use that ) for things like the clojure-maven-plugin, so >> that I can use the same IT test projects injecting different versions of >> clojure. >> >> >> On 10 Feb 2014, at 15:21, Jason van Zyl wrote: >> >>> I don't agree with this change and I think it potentially destabilizes >>> the most valuable resource we have for testing stability, but if you >>> don't see this as an issue then I leave it to you to decide. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
