Stephan, This is exactly what I'm saying - by rebuilding the plugins with the new JARs, when Maven is run for other projects, the newly built plugin will be used. So if we move to bootstrapping Maven as part of the gump process, this should come naturally.
I believe it adheres to overrides as it uses exactly the same code, but I haven't run any official tests. Cheers, Brett > -----Original Message----- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: Thursday, 12 February 2004 6:45 PM > To: [EMAIL PROTECTED] > Subject: Re: Maven & Gump (again) > > > >> But whoever is responsible for the JUnit plugin would like to > >> know that things break. We should try to make this work for > >> Maven in the longer run. > > On Thu, 12 Feb 2004, Brett Porter <[EMAIL PROTECTED]> wrote: > > > Absolutely - this is why the plugin needs to be rebuilt with the > > latest jars. > > Sometimes failures are more difficult than that. The plugin > may compile but fail to execute with a new lib. So Gump > should be able to override the jars used by the Maven plugins > as well - sooner or later. Do plugins adhere to jar overrides? > > Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
