Re: MNG-4483
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 benjamin.bentm...@udo.edu 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 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 change until it is. Maybe this is a 3.1 thing. As per MNG-4390, unknown elements cause warnings but don't fail the build, thereby easing side-by-side use of different Maven versions. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: MNG-4483
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. On Fri, Apr 23, 2010 at 3:19 AM, Benjamin Bentmann benjamin.bentm...@udo.edu 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 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 change until it is. Maybe this is a 3.1 thing. As per MNG-4390, unknown elements cause warnings but don't fail the build, thereby easing side-by-side use of different Maven versions. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl --
Re: MNG-4483
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 change until it is. Maybe this is a 3.1 thing. As per MNG-4390, unknown elements cause warnings but don't fail the build, thereby easing side-by-side use of different Maven versions. Benjamin - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : MNG-4483
+1 - Message d'origine De : Paul Benedict pbened...@apache.org À : Maven Developers List dev@maven.apache.org 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 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 .mvn. Paul - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Re : MNG-4483
+1 for .mvn and backward compatibility with .m2 if not found 2010/4/22 Julien HENRY henr...@yahoo.fr +1 - Message d'origine De : Paul Benedict pbened...@apache.org À : Maven Developers List dev@maven.apache.org 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 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 .mvn. Paul - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Re : MNG-4483
+1 Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net On Thu, Apr 22, 2010 at 6:00 PM, nicolas de loof nicolas.del...@gmail.comwrote: +1 for .mvn and backward compatibility with .m2 if not found 2010/4/22 Julien HENRY henr...@yahoo.fr +1 - Message d'origine De : Paul Benedict pbened...@apache.org À : Maven Developers List dev@maven.apache.org 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 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 .mvn. Paul - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Re : MNG-4483
On Thu, Apr 22, 2010 at 12:00 PM, nicolas de loof nicolas.del...@gmail.com 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: MNG-4483
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 pbened...@apache.org wrote: 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 .mvn. Paul - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: MNG-4483
Brian, 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. Paul On Thu, Apr 22, 2010 at 11:35 AM, Brian Fox bri...@infinity.nu wrote: 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 pbened...@apache.org wrote: 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 .mvn. Paul - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re : Re : MNG-4483
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 wsm...@gmail.com À : Maven Developers List dev@maven.apache.org Envoyé le : Jeu 22 avril 2010, 18 h 16 min 46 s Objet : Re: Re : MNG-4483 On Thu, Apr 22, 2010 at 12:00 PM, nicolas de loof ymailto=mailto:nicolas.del...@gmail.com; href=mailto:nicolas.del...@gmail.com;nicolas.del...@gmail.com 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 - To unsubscribe, e-mail: href=mailto:dev-unsubscr...@maven.apache.org;dev-unsubscr...@maven.apache.org For additional commands, e-mail: href=mailto:dev-h...@maven.apache.org;dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: MNG-4483
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 logic. If they don't, then they might be parsing/updating the wrong file with non-obvious impacts to the user. I just wonder if it's really worth the hassle? Having parallel but different settings.xml seems to be the only benefit and I wonder if that alone wouldn't cause more support problems. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: MNG-4483
Just to play devil's advocate, if you run maven then sync your tool, maven will use .mvn, the IDE/tool will only check .m2. []s Gus On Thu, Apr 22, 2010 at 9:45 AM, Paul Benedict pbened...@apache.org wrote: Brian, 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. Paul On Thu, Apr 22, 2010 at 11:35 AM, Brian Fox bri...@infinity.nu wrote: 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 pbened...@apache.org wrote: 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 .mvn. Paul - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: MNG-4483
FAIL! I was a bit too late :) On Thu, Apr 22, 2010 at 10:04 AM, Brian Fox bri...@infinity.nu 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 progress. Because now every tool that cares about this folder needs to implement that same logic. If they don't, then they might be parsing/updating the wrong file with non-obvious impacts to the user. I just wonder if it's really worth the hassle? Having parallel but different settings.xml seems to be the only benefit and I wonder if that alone wouldn't cause more support problems. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: MNG-4483
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 bri...@infinity.nu 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 progress. Because now every tool that cares about this folder needs to implement that same logic. If they don't, then they might be parsing/updating the wrong file with non-obvious impacts to the user. I just wonder if it's really worth the hassle? Having parallel but different settings.xml seems to be the only benefit and I wonder if that alone wouldn't cause more support problems. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: MNG-4483
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 pbened...@apache.org wrote: 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 bri...@infinity.nu 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 progress. Because now every tool that cares about this folder needs to implement that same logic. If they don't, then they might be parsing/updating the wrong file with non-obvious impacts to the user. I just wonder if it's really worth the hassle? Having parallel but different settings.xml seems to be the only benefit and I wonder if that alone wouldn't cause more support problems. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: MNG-4483
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 opinion if it is just for aesthetics. Would be nice, but not really important enough. 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 change until it is. Maybe this is a 3.1 thing. I think if it is done with a good reason, the tools will catch up soon enough - good tools would already support relocating the settings.xml file to match maven's arguments and the repository to match the entry in settings - at that point they'd only be adjusting to a new settings.xml format. The workaround for users is there if one of their tools doesn't. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
