IMO publishing to central/acrhiva would involve publishing the "richest" format available. Based on use-agent identification (or lack of a given request param indicating old-style client) the repository should be able to down-transform a v5 pom to a v4 pom "on the fly" ? We're not going to be losing semantic backward compatibility on any of the changes I've seen suggested yet ?
Also, did I miss the bit where someone explained why the whole "how to build" section cannot be stripped away upon publication ? I don't understand why that means we need multuiple files. I'm exposed to "the competition" at @dayjob these days, and I must say I think reducing verobosity and duplication is /the/ most important feture of a v5 pom for me. Kristian 2013/11/25 Manfred Moser <manf...@mosabuam.com> > > On Sunday, 24 November 2013, Manfred Moser wrote: > > > >> > >> > By separating "consumption" and "production" metadata formats, we'll > >> be > >> > able to evolve production format more aggressively. For example, it > >> > would be nice to have Tycho-specific configuration markup inside > >> <build> > >> > section. This is not currently possible because all poms must be > >> > compatible with the same model. > >> > >> I like the idea of consumptions specifics. It would be great if we could > >> agree/define some sort of standard on how to declare suitability for > >> artifacts for certain deployment scenarios .. > >> e.g. it is jar suitable for Java 6, 7, 8, 9 or what, what about running > >> on > >> Android, or on some embedded Java version profile. > >> > >> I dont believe that the previous approaches of using classifiers is just > >> not powerful enough. And I also agree that we should potentially just > >> stick to the existing format. > >> > >> E.g. nothing stops us from declaring a standard for e.g. for a bunch of > >> properties like > >> > >> <properties> > >> <runtime.android>true</runtime.android> > >> <runtime.java6>true</runtime.java6> > >> </properties> > >> > >> or > >> <properties> > >> <runtime.android>false</runtime.android> > >> <runtime.java6>false</runtime.java6> > >> <runtime.java7>true</runtime.java7> > >> </properties> > >> > >> > > How is that any different from having a modelVersion 5.0.0? (Other than > > not > > giving the benefit of a schema change) > > > It probably isnt different ;-) > > manfred > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
