[ 
https://jira.codehaus.org/browse/MNG-4525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul Benedict updated MNG-4525:
-------------------------------

    Fix Version/s:     (was: Issues to be reviewed for 3.x)

> Separate settings for infrastructure related tasks
> --------------------------------------------------
>
>                 Key: MNG-4525
>                 URL: https://jira.codehaus.org/browse/MNG-4525
>             Project: Maven
>          Issue Type: Improvement
>         Environment: *
>            Reporter: Oskar Carlstedt
>
> Hello!
> I've been using Maven for a long time now and so to say, I almost love it. 
> So, first of all. Thanks for a really great product and a superb work.
> During my projects I've seen some situations that Maven can't handle in a 
> good way. Most situations are about changes in the IT infrastructure. It can 
> be as simple things as changing the domain or path to the SCM. The most ideal 
> situation would be if settings related to infrastructure could be saved in a 
> global settings file read by Maven. In such way it would be possible to use 
> global infrastructure configurations for all projects. E.g. when changing the 
> domain of an SCM url, it is just about changing one parameter in a global 
> settings file.
> Some posts say this doable by using parent projects. But when a parent 
> project is released, then it is not possible to change any part of it that 
> does not affect the actual build, without updating the repository version, or 
> maybe more correct adding a new minor version. Changing the version of a 
> parent project is not possible without updating each child project to use the 
> new parent. If it was possible to use version scopes of parent project, this 
> would be doable. But, I agree to all the critics about this, then it would be 
> difficulties in specifying an exact build.
> So the feature request is about adding an extra level of settings that does 
> not affect the build itself. I'm aware of that this feature can be misused 
> and make builds hard to understand. But I see it as a must in commercial 
> environments that changes over time.
> Best regards
> Oskar Carlstedt



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to