Hi Benson! Txs for pushing that, looks really good!.
As for compat: I read your proposal this way: pom5 projects can only be built with mvn3.1 or mvn4 (or whatever we call it) but while installing/deploying, a pom-4.0 will be created which can be _consumed_ as dependencies even by mvn2 and/or mvn3, right? As for the repo managers: *) distributionManagement repos should work with pom5. I think we can assume that Archiva and Nexus will support that. It's really not too much a problem. *) proxy Repos for mvn2/mvn3 will at least see and proxy the pom-4.0.0. So anyone behind a closed company firewall is still able to build in compat mode. Maybe he is not able to build the latest and greatest pom5 project, but thats not our fault then. LieGrue, strub --- On Wed, 7/27/11, Vincent Siveton <[email protected]> wrote: > From: Vincent Siveton <[email protected]> > Subject: Re: POM5 proposal > To: "Maven Developers List" <[email protected]> > Date: Wednesday, July 27, 2011, 5:16 AM > Hi Benson > > Thanks for your proposal! > > IMHO the pom5 should include some tags like <wiki/> > or > <qualityManagement/> and the javadoc <api/> > see MPIR-149 MJAVADOC-32 > > Cheers, > > Vincent > > 2011/7/24 Benson Margulies <[email protected]>: > > Since I can't edit the Wiki, I created: > > > > https://docs.google.com/document/d/1k3E4vx_4cKJ4zzksVM4oROX3Dffsh0Q4VOGVjd3oUto/edit?hl=en_US > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
