Re: MNG-4483

2010-04-26 Thread Jason van Zyl
On Apr 26, 2010, at 11:43 AM, Paul Benedict wrote: > Could this be slated for beta-2? And if it is decided to be not the > right time, bump it to 3.1? > I think we should focus on fixing issues for 3.0, but that doesn't mean we can't start thinking and making prototypes for other features. >

Re: MNG-4483

2010-04-26 Thread Paul Benedict
Could this be slated for beta-2? And if it is decided to be not the right time, bump it to 3.1? On Fri, Apr 23, 2010 at 3:19 AM, Benjamin Bentmann wrote: > Brett Porter wrote: > >> However, it is important to be able to change the settings.xml file in >> future, and the best way to do that and st

Re: MNG-4483

2010-04-23 Thread Benjamin Bentmann
Brett Porter wrote: However, it is important to be able to change the settings.xml file in future, and the best way to do that and still support Maven 2 is by having a second location. Is Maven 3 already forwards compatible with reading the settings file? If not yet, I wouldn't consider this

Re: MNG-4483

2010-04-22 Thread Brett Porter
On 23/04/2010, at 5:08 AM, Brian Fox wrote: > The neat-nick in me says no, but I'm also not going to rename > repo1.maven.org/maven2 to /maven3 either. I'm just playing devil's > advocate here to point out that there are additional considerations > than simply changing the maven core logic. Same

Re: MNG-4483

2010-04-22 Thread Brian Fox
The neat-nick in me says no, but I'm also not going to rename repo1.maven.org/maven2 to /maven3 either. I'm just playing devil's advocate here to point out that there are additional considerations than simply changing the maven core logic. On Thu, Apr 22, 2010 at 2:36 PM, Paul Benedict wrote: > B

Re: MNG-4483

2010-04-22 Thread Paul Benedict
Brian, Then the current situation should be viewed as acceptable? The ".m2" directory, although an artifact of Maven 2, continues to be the home directory for Maven 3. Paul On Thu, Apr 22, 2010 at 12:04 PM, Brian Fox wrote: >> What ramifications could exist if .m2 is the fallback? It would be a

Re: MNG-4483

2010-04-22 Thread Gustavo Hexsel
FAIL! I was a bit too late :) On Thu, Apr 22, 2010 at 10:04 AM, Brian Fox wrote: > > What ramifications could exist if .m2 is the fallback? It would be an > > easy upgrade path. My point is, it's odd Maven 3 has an "m2" user > > directory -- nothing technically incorrect; just a vestigial of

Re: MNG-4483

2010-04-22 Thread Gustavo Hexsel
the ramifications for > > all the tools that would have to be updated. Is it worth it? > > > > On Thu, Apr 22, 2010 at 11:14 AM, Paul Benedict > wrote: > >> 3.0-beta-1 being a beta release, it's getting close to GA. I was > >> wondering can MNG-4483 be a

Re: MNG-4483

2010-04-22 Thread Brian Fox
> What ramifications could exist if .m2 is the fallback? It would be an > easy upgrade path. My point is, it's odd Maven 3 has an "m2" user > directory -- nothing technically incorrect; just a vestigial of > progress. Because now every tool that cares about this folder needs to implement that same

Re : Re : MNG-4483

2010-04-22 Thread Julien HENRY
1) check if .mvn exists 2) if .mvn doesn't exist then check if .m2 exists 3) if .m2 doesn't exist then create .mvn and use it ++ Julien - Message d'origine > De : Wendy Smoak > À : Maven Developers List > Envoyé le : Jeu 22 avril 2010, 18 h 16 min 46 s >

Re: MNG-4483

2010-04-22 Thread Paul Benedict
his sounds easy on the maven side, but what are the ramifications for > all the tools that would have to be updated. Is it worth it? > > On Thu, Apr 22, 2010 at 11:14 AM, Paul Benedict wrote: >> 3.0-beta-1 being a beta release, it's getting close to GA. I was >> wonder

Re: MNG-4483

2010-04-22 Thread Brian Fox
This sounds easy on the maven side, but what are the ramifications for all the tools that would have to be updated. Is it worth it? On Thu, Apr 22, 2010 at 11:14 AM, Paul Benedict wrote: > 3.0-beta-1 being a beta release, it's getting close to GA. I was > wondering can MNG-4483 be a

Re: Re : MNG-4483

2010-04-22 Thread Wendy Smoak
On Thu, Apr 22, 2010 at 12:00 PM, nicolas de loof wrote: > +1 for .mvn and backward compatibility with .m2 if not found Wouldn't it _create_ .mvn if it's not found? Otherwise what's going to happen the first time you use m3 on a new machine? -- Wendy --

Re: Re : MNG-4483

2010-04-22 Thread Arnaud Héritier
> > > +1 > > > > > > > > - Message d'origine > > > De : Paul Benedict > > > À : Maven Developers List > > > Envoyé le : Jeu 22 avril 2010, 17 h 14 min 15 s > > > Objet : MNG-4483 > > > > > > 3.0-beta-1 being a beta

Re: Re : MNG-4483

2010-04-22 Thread nicolas de loof
+1 for .mvn and backward compatibility with .m2 if not found 2010/4/22 Julien HENRY > +1 > > > > - Message d'origine > > De : Paul Benedict > > À : Maven Developers List > > Envoyé le : Jeu 22 avril 2010, 17 h 14 min 15 s > > Objet : MNG-

Re : MNG-4483

2010-04-22 Thread Julien HENRY
+1 - Message d'origine > De : Paul Benedict > À : Maven Developers List > Envoyé le : Jeu 22 avril 2010, 17 h 14 min 15 s > Objet : MNG-4483 > > 3.0-beta-1 being a beta release, it's getting close to GA. I was wondering > can MNG-4483 be addressed? I

MNG-4483

2010-04-22 Thread Paul Benedict
3.0-beta-1 being a beta release, it's getting close to GA. I was wondering can MNG-4483 be addressed? I don't think Maven can keep the .m2 user directory exclusively -- it could be a good fallback for compatibility -- but it should be looking for .m3 or .