[ 
https://jira.codehaus.org/browse/MNG-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=302919#comment-302919
 ] 

Aaron Digulla commented on MNG-2553:
------------------------------------

I have a different use case: I often need to deploy existing third party 
projects to our internal repository. Not all of them have 
distributionManagement elements and not all of them use your properties-scheme.

Currently, I have to find the parent POM (and possibly check out another 
project), add the distributionManagement there, deploy it and only then I can 
deploy the project.

It would be really useful to be able to create a profile which just contains a 
distributionManagement for my internal repo so I can deploy anything into it 
without having to edit the original POM.

Because that either gives me a file that I must not check in (so the project is 
always in a "needs commit" state) or, even worse, I might accidentally commit 
it and ruin the day for other people.

Please reconsider.
                
> Maven Local Settings Model should allow configuration of distributions 
> (distributionManagement)
> -----------------------------------------------------------------------------------------------
>
>                 Key: MNG-2553
>                 URL: https://jira.codehaus.org/browse/MNG-2553
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>          Components: Settings
>    Affects Versions: 2.0.4
>            Reporter: Jimisola Laursen
>
> There is a good use case where this would be very useful.
> E.g. I develop a plugin in mojo-sandbox and want to test it in an environment 
> other than the one that I developed it on (e.g. a computer at work). I check 
> out the plugin to this, build and then want to deploy to another repository 
> (e..g a company's internal repository). I don't want to fiddle with the 
> pom.xml of the plugin, just refer to a profile in settings.xml.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to