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
