On Tuesday, 14 February 2012, Andrew Todd <andrew.todd...@gmail.com> wrote: > Apologies if this has already been rehashed to death, but I have been > trying to trace the arc of Maven mixin development over the past few > years, and was wondering what happened.
They kind of need a Pom version change to work... Every time we hit the Pom version change problem the 3.0.0 to 4.0.0 transition flashbacks put a blocker on migration, and the thought of deploying two poms, with the resulting slow-down for people depending on legacy artifacts, or people with maven 3.0 or 2.x trying to use new artifacts stymies progress. There really is only one viable solution so far, and that is less than perfect... Add on top that with the (deploy two poms) solution, it only gets us one version transition, so it does not scale... That is to have a version 6.0.0 Pom we'd need to deploy three poms for each artifact. The end result is we need a version 5.0.0 format that we are sure can be extended (future proof) and then the two poms deployment is perhaps acceptable - stephen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
