John Casey wrote: > > > On 5/24/11 8:25 AM, Brian Fox wrote: >> 2011/5/24 Arnaud Héritier<aherit...@gmail.com>: >>> Before talking about a specific change in the model like the addition of >>> mixins (which may be cool but not critical) did we : >>> - studied that we had everything necessary to manage new versions of >>> POMs with something a little bit dynamic inside the core and all that is >>> necessary on repositories side ? >>> - studied if we couldn't start by really simple issues that may already >>> do a very useful 3.1 version like the addition of global exclusions ? >>> >> >> I didn't read the proposal in detail yet, but my initial concern was >> on pom compat as well. > > 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...
Hmmm. And what about semantical compatibility? E.g. if a newer pom version declares global excludes, the resulting target might be completely different if you build with an older Maven version. This might even be the case if one of the dependencies is using a newer POM only. I just want to emphasis that such a change is not of technical nature only. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
