Ah, I forgot that it's defined in the super pom. I was thinking that it was in the code somewhere.
I think adding the central repo to the default global settings would be a good start. Would it even need to be commented out? If it is defined in both places, I'm assuming that the one in the settings.xml take priority? Brian Fox wrote: > I assume you want to make it easier for people to get the correct > settings? Moving it from the super pom could have unexpected side > effects, but what if we put the default "boiler plate"[1] > configuration for that into the default settings.xml commented out? I > think this would solve the main visibility problem without affecting > runtime. > > [1] > http://www.sonatype.com/books/nexus-book/reference/maven-sect-single-group.html#ex-maven-nexus-simple > > On Mon, Apr 26, 2010 at 6:41 PM, Benjamin Bentmann > <benjamin.bentm...@udo.edu> wrote: >> Paul Gier wrote: >> >>> Would there be any problems if the central repo definition was moved out >>> of the >>> Maven internals and into the default settings.xml [1]? >> I assume you refer to the global settings file shipped inside the Maven >> installation directory. The one issue I know about is that embedders of >> Maven like M2E don't have a CLI-style installation directory and hence no >> global settings file. Not impossible to solve but it needs to be considered. >> >> >> 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 > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
