> > I think doing some sort of on-the-fly translation into a 4.0.0 POM purely > to be deployed for backwards compat would be enough here...though we may > want to explore how we could make Maven smart enough to say, "I can't read > this POM, use a later version" or somesuch... > > Why only consider deployed POM for backward compatibility ? Same system may use older maven somewhere else and still share the localRepository. We should either always translate the POM to 4.0.0 even during install, or do some sort of double-versioning.
- POM 4+ was Re: Moving forward with mixins Arnaud Héritier
- Re: POM 4+ was Re: Moving forward with mixins Brian Fox
- Re: POM 4+ was Re: Moving forward with mixins John Casey
- Re: POM 4+ was Re: Moving forward with mixin... nicolas de loof
- Re: POM 4+ was Re: Moving forward with mixin... Arnaud Héritier
- Re: POM 4+ was Re: Moving forward with m... Stephen Connolly
- Re: POM 4+ was Re: Moving forward w... John Casey
- Re: POM 4+ was Re: Moving forwa... Stephen Connolly
- Re: POM 4+ was Re: Moving forward w... nicolas de loof
- Re: POM 4+ was Re: Moving forwa... Arnaud Héritier
- Re: POM 4+ was Re: Moving f... Stephen Connolly
- Re: POM 4+ was Re: Moving forwa... Stephen Connolly
- Re: POM 4+ was Re: Moving forward w... Brian Fox
- Re: POM 4+ was Re: Moving forward with mixin... Jörg Schaible