Hi, I think there is no change in maven 3.0 about settings.xml ? Actually there are several problems (from my point of view) : * Mirrors don't support something to catch all releases repo or all snasphots repo. ** It creates a problem because you have to use a unique group in repo managers and then you download SNAPSHOTs versions for CLI plugins. ** Using repoIDs for mirror is unusable because repoIDs aren't unique * Profiles are confusing and can be source of problems if they are badly used. Moreover many things have to be put in profiles (repositories for example) whereas it could be outside. * There is no inheritance/mixins mechanisms to share settings accross an organization / a company / a project thus it is difficult to deploy/keep up to date them
Not really related to settings but to the infrastructure and how maven works we talked several times about having several local repositories. The most interesting feature was to have one dedicated for each build and binaries was moved to another when all the project was build. It could allow to have a form of transaction in the build to not install a part of a project and having inconsistencies. (The problem also exists for deployment - how could we deploy all binaries only when the project is entirely built). I'm pushing all those questions because you are reviewing our backlog and I don't know if some of these remarks are already filled in Jira. Cheers, Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net
