+1 if we help java.net to throw the m1 repo they are always using.
Arnaud
On Tue, Jul 21, 2009 at 9:51 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> +1, just make sure that when you kill it, it ends up dead ;-)
>
> 2009/7/20 Jason van Zyl
>
> > Hi,
> >
> > Maven 2.x has been
+1, just make sure that when you kill it, it ends up dead ;-)
2009/7/20 Jason van Zyl
> 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 reposi
+1 since when is this 'deprectated'? 4 years?
LieGrue,
strub
--- On Mon, 7/20/09, Jason van Zyl wrote:
> From: Jason van Zyl
> Subject: Stop support for legacy repository layout in 3.x
> To: "Maven Developers List"
> Date: Monday, July 20, 2009, 8:48 PM
&
+1 for reasons already outlined
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
+1. The sun repo was the only one that caused me concern (they do
still publish some projects there) but this can be dealt with.
On Mon, Jul 20, 2009 at 11:09 PM, Brett Porter wrote:
>
> On 21/07/2009, at 1:04 PM, Jason van Zyl wrote:
>
>> On 20-Jul-09, at 8:14 PM, Brett Porter wrote:
>>
>>> Is th
On 21/07/2009, at 1:04 PM, Jason van Zyl wrote:
On 20-Jul-09, at 8:14 PM, Brett Porter wrote:
Is this just to remove legacy support, or remove configurability of
the layout altogether (say, if we wanted to introduce something
different in the future?)
Just the legacy support, not the p
On 20-Jul-09, at 8:14 PM, Brett Porter wrote:
Is this just to remove legacy support, or remove configurability of
the layout altogether (say, if we wanted to introduce something
different in the future?)
Just the legacy support, not the pluggable mechanism itself.
- Brett
On 21/07/2009
Is this just to remove legacy support, or remove configurability of
the layout altogether (say, if we wanted to introduce something
different in the future?)
- Brett
On 21/07/2009, at 4:48 AM, Jason van Zyl wrote:
Hi,
Maven 2.x has been out for quite some number of years now, and I
want
+1 (non binding)
And also, some of MRMs are of great use on laptops too, due to their
small memory footprints, and they are of great help with "decoupling" you
from "work" to "home" schemes ;)
~t~
On Mon, Jul 20, 2009 at 10:07 PM, Jason van Zyl wrote:
>
> On 20-Jul-09, at 3:12 PM, nicolas de lo
On 20-Jul-09, at 3:12 PM, nicolas de loof wrote:
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
+1
We've carried this format for several years now, and IMO it's widely
understood to be deprecated. I think it's safe to say that most Maven
users are on Maven 2.x by now, so leaving the legacy format in place
doesn't have much value.
Users who really still need this feature can always run
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 conver
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 ma
13 matches
Mail list logo
