2009/12/29 Arnaud HERITIER <aherit...@gmail.com> > > > > > > > > > > > > > > I agree. The problem will be in 3.1. We'll be able to remove things > > > deprecated in 3.0 but nothing more. > > > We'll have to see what we'll do if we have big changes. > > > For me the most important problem to work on (post 3.0), will be how we > > > manage different versions of POMs and metadata. This will have an > > important > > > impact for our users. > > > > > > cheers, > > > > > > > > I think this depends on what model changes we want. > > > > My Idea is to deploy the new version pom as a pom with a classifier and > > co-deploy a v4.0.0 translated pom as the pom without a classifier. > > > > That way we can have m4 look for the pom with classifier (if missing it > > looks for the v4.0.0 pom) everything older will only see the pom without > a > > classifier > > > > -Stephen > > > > P.S. I think Brian Fox had a similar idea > > > > > > In the future if we have 4.0.0, 4.1.0, 4.2.0 ... models, we'll try to > deploy one per version with a different classifier ? > And what will happen when we'll do a change in a model that we cannot > convert to 4.0.0 model? We don't deploy it ? > > We deploy the dependencies as the 4.0.0 model, we strip out the parent info and fully resolve the pom for the 4.0.0 model
For the pom with classifier, we use a scheme that allows us to plug in extensibility so that we only need one classifer ever... we call the classifier "build" and the pom without classifier is just for dependency info > Arnaud >
