I agree, but as I understood from another message, the updated dependency to TestNG would have to be reversed if we lock the surefire plugin down to 2.3. If that's not a major issue, I guess that's the easiest way to solve the problem.
Nils-H On Feb 17, 2008 3:22 AM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On Feb 16, 2008 12:29 PM, Nils-Helge Garli Hegvik <[EMAIL PROTECTED]> wrote: > > If > > I set the plugin version back to the previous release (2.3) it runs > > perfectly. But with the new 2.4 version, the test breaks... 2.4.1 > > doesn't work either. So what do we do? I guess hard coding the version > > to 2.3 isn't a very good option? > > Actually all plugin versions should be locked down so you're not > surprised by the auto-updates. Adding a <version> for surefire is a > good idea. > > (The Maven devs have already acknowledged that auto-updating was a bad > idea... It's likely to be removed in 2.1.) > > -- > Wendy > > > --------------------------------------------------------------------- > 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]
