Legacy layout is still used at http://download.java.net/maven/1/ by some project, including some standard Java API (activation, mail, persistence...) can we expect them to migrate to http://download.java.net/maven/2/ ? Maybe some evangelism / lobbying could help ;)
A repo manager can safely convert such repo on the fly to default layout, but this is an extra infrastructure setup that mostly target entreprises, not considering standalone (laptop) use. For this reason I'm only +0 with this proposal. As the repository is hidden by Mercury abstraction (AFAIK), would this really make Maven simplier ? Cheers, Nicolas 2009/7/20 Jason van Zyl <jvan...@sonatype.com> > Hi, > > Maven 2.x has been out for quite some number of years now, and I wanted to > float the idea of stopping support for the legacy repository format in 3.x? > > There are tools now that can convert repository formats, and I believe all > of the three popular repository managers support dynamic mapping to legacy > format for Maven 1.x clients. > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > http://twitter.com/SonatypeNexus > http://twitter.com/SonatypeM2E > ---------------------------------------------------------- > > What matters is not ideas, but the people who have them. Good people can > fix bad ideas, but good ideas can't save bad people. > > -- Paul Graham > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
