Sent from my iPhone
> On 16 Oct 2016, at 00:07, Christian Schulte <c...@schulte.it> wrote: > >> Am 10/16/16 um 00:57 schrieb Stephen Connolly: >> We only have to generate a "consumer pom" in modelVersion 4.0.0... and that >> need only be best effort, and will be generated off the PDT ... the new Pom >> schema is what drives generating the PDT > > If a scope is used not known to POM 4.0.0, just discard it during > generating POM 4.0.0. Nope. No need. The consumer Pom will only list the direct dependencies from the PDT for the "primary" artifact... they will all be just compile scope. > Things like that. Someone wanting to support > building with Maven < 5 as well can provide a 4.0.0 POM manually besides > the new build pom. My question is really: Say I have a bunch of projects, half need Maven 3 half need Maven 5... do I have to use something like rbenv to switch Maven every time I Move directory? Or can I just leave Maven home as Maven 5 and it will work for both projects? > Any thoughts about how to name that new build pom? project.mvn or pom.mvn But only if we move to a non-xml DSL If we are still XML then I say stick with pom.xml and sniff the modelVersion > maven.xml? So someone can have pom.xml besides maven.xml and can build > with Maven < 5 and >= 5. For remote deployment Maven >= 5 should be > used. We cannot stop someone from deploying with Maven < 5 and then one > more time again with Maven >= 5. Maybe repository managers need to be > aware of that somehow. Disallow deployments with Maven < 5 or disallow > deployments with Maven >= 5 if already deployed with Maven < 5. Or just > name the new file 'pom.xml' again to avoid that situation right from the > start. Maven < 5 just cannot parse it and fails. Best we can do, I think. > > Regards, > -- > Christian > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
