@Jason @all Can you tell me why we want to release Maven 3.4.0 and not Maven 4.0.0? I guess Maven 4.0.x may finalize Model Version 4.0.0 era. Do you have other plans with Maven 4.x?
Back to modelVersion and consumer POM. The consumer pom is a subset of normal POM. Keep using consumer POM with current schema would not break the current users and therefore I think the schema should be currently same. Even if the consumer POM would be smaller than you project POM, it's still ok. Maybe later users would have chance to release consumer POM under modelVersion 5.0.0, 6.0.0, etc. Or lower version preferably chosen by our plugins. On 8/28/16, Tibor Digana <[email protected]> wrote: > Hi Robert, as I am reading your comments, I see the situation is not > be so tragic :) > What about to let m-deploy-p and m-release-p to decide on modelVersion > of consumer project as the minimum version. If for instance a new > scope value is available in <dependency/> of your project POM, then > the plugin would decide to align modelVersion to higher than 4.0 and > lower or equal to modelVersion in reactor's parent POM. > This would guarantee that the consumer POM has minimum conflicts and > maximize consumers community who can use this POM from Maven Central > > To override the modelVersion in Consumer POM: > > <configuration> > <targetConsumerModelVersion/> > </configuration> > > -- > Cheers > Tibor > > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Re-POM-Model-version-4-1-0-in-3-4-0-SNAPSHOTs-tp5878254p5878961.html > Sent from the Maven Developers mailing list archive at Nabble.com. -- Cheers Tibor --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
