Quoting Jason van Zyl (2012-07-30 17:43:13) > On Jul 30, 2012, at 10:10 AM, Stephen Connolly wrote: > > > The only reason to do this from my PoV is if the plugin requires features > > only available in Maven 3. > > > > There are still a significant number of users who use Maven 2.2.1, yeah I > > would love to get them to jump up to 3.0.4, but I acknowledge that is > > something that may be beyond their control. Forcing plugin dependencies up > > without a valid driving requirement is just forcing unnecessary pain on the > > end users. > > > > IMHO features should drive the upgrading of dependencies, nothing else. > > > > +1 > > There is little value in updating plugins to use Maven 3.x components for the > sake of it. The reason we spent so much time making sure that 3.x runs older > components was to ensure no one has to do this.
Apparently sending out inquiries before leaving for 2 week vacation was not ideal :-) So my view was somewhat different. I would hope you would like to get rid of direct dependencies on old Maven 2.x code. And as you've said Maven 3.x runs older components just fine, so this wouldn't have to be "Let's switch tomorrow". Instead it could be a gradual maintenance cleanup. Removing dead and/or unmaintained code. But I understand people using Maven 2.2.1 would be unable to upgrade their dependencies to new versions using Maven 3.x artifacts (or at least it's not a supportable use-case even though it might work). In any case, you've made your opinion clear so I have a different question then :-) Is there any timeframe you have in mind for this transition to happen? 2 years? 5 years? 10 years? Never? I *assume* there will come a time where 2.0.11 and 2.2.1 will have to die (i.e not be featured as download options). I would guess the transition would start at least then. -- Stanislav Ochotnicky <[email protected]> Software Engineer - Base Operating Systems Brno PGP: 7B087241 Red Hat Inc. http://cz.redhat.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
