I think what he is saying is that plugins out there may declare a newer version of p-u (like mdep) that tested to work with that version ok (so we thought) because it was really using the mvn core version. If suddenly you allow plugins to use their own declared versions, they may suddenly not work.
It's a risk, but I think it needs to be done. The only thing we can do is allow the use in the snapshot, and then test the plugins to see if they work or suddenly break and see if we can get fixes timed to release with 2.0.6. After all, the fix would be to just roll back the p-u version to whatever 2.0.5 enforced in the broken plugin's pom so it should be easy (especially if we go back to the release and make a patch release from the tag) --Brian -----Original Message----- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Monday, March 12, 2007 12:01 PM To: Maven Developers List Subject: Re: Moving toward 2.0.6 On 12 Mar 07, at 6:15 AM 12 Mar 07, Jerome Lacoste wrote: > On 3/12/07, Kenney Westerhof <[EMAIL PROTECTED]> wrote: >> >> I think we should require the hiding of p-u 1.4.1 in 2.0.6, or let it >> still use 1.1. All previous releases (except for beta releases) use >> p-u 1.1. I'm afraid exposing p-u 1.4.1 will break more than just >> surefire. > > > I agree. > > But even hiding 1.1 will probably affect some plugins that used to > refer to a higher version of p-u without knowing it wasn't really in > use. > No it shouldn't affect them at all. Plugins can specify the exact version they needed. The version used in the core will be invisible. Jason. > It's a smaller problem. I am curious as to see how many plugins will > be affected. > > J --------------------------------------------------------------------- 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]
