On 2009-12-30, at 3:57 AM, Arnaud HERITIER wrote: > Hi, > > I think there is no change in maven 3.0 about settings.xml ?
There are no changes in settings.xml. There will be no changes in settings.xml for 3.0 at this point. > 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 > There's already a proposal for much of this. I know Brian wanted to talk about it so I'll leave that to him. Regardless this is unlikely to change between now and 3.0. > 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 The infrastructure for having multiple "local" repositories is already implemented in the core. This was to simplify IDE integration primarily but would allow multiple local repositories if you wanted on only for snapshots versus releases. > - how could we deploy all binaries only when the project is entirely built). This will also not be terribly hard to fix but is a major behavioural change and will require quite a bit of testing. > > > 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. We're not going to anything until it's cleaned up. It's probably pretty near impossible for anyone with only 20 minutes to find anything. Our website, JIRA and Confluence are all not very well organized. So as part of the 3.0 the code, testing, and visibility to the outside world is primarily what I'm going to focus. I think the only sane thing to do is try to move people forward to a well tested replacement for the 2.x line which is a dead end. > > Cheers, > > > Arnaud Héritier > Software Factory Manager > eXo platform - http://www.exoplatform.com > --- > http://www.aheritier.net Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl ---------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
