Quoting Chris Graham (2012-07-30 15:43:31) > I work with a lot of older (sometimes out of service software [customers pay > a fortune but are prepared to live with it]) so I'm generally a fan of the > lowest common denominator.
Indeed nothing wrong with it > > What do you hope to achieve by the? Each released version still using Maven 2.x code prolongs its life. If you never stop supporting it, people will never start moving to new versions :-) I would expect people who want to live with old (or even out-of-service) software don't need (or want) to live with new plugins. Or so I would guess. But I understand they can give you task which requires feature of a new plugin, but new plugin would then need new Maven which they don't want to update not to break their other builds. There are solutions for that though (parallel installation being one) > Are there any specific outstanding issues that need this change to solve? Nothing specific, just looking 10 years into the future where Maven 2.x still lives happily. -- 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]
