[
http://jira.codehaus.org/browse/MNG-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=188854#action_188854
]
Rogan Creswick commented on MNG-2553:
-------------------------------------
We've worked around this by moving the repository details to settings.xml as
properties:
{code:xml}
<settings>
...
<profiles>
<profile>
...
<properties>
<releases.url>http://10.0.0.20:8081/nexus/content/repositories/releases</releases.url>
<snapshots.url>http://10.0.0.20:8081/nexus/content/repositories/snapshots</snapshots.url>
</properties>
</profile>
...
</profiles>
...
</settings>
{code}
then, in the pom:
{code:xml}
<distributionManagement>
<snapshotRepository>
<id>snapshots</id>
<name>Snapshots</name>
<url>${snapshots.url}</url>
</snapshotRepository>
<repository>
<id>releases</id>
<name>Releases</name>
<url>${releases.url}</url>
</repository>
</distributionManagement>
{code}
It's not ideal, but at least external users can define those properties in a
local settings.xml, or override them in a parent pom (I believe) and maven can
still be used for non-deploy tasks even if they aren't defined.
> Maven Local Settings Model should allow configuration of distributions
> (distributionManagement)
> -----------------------------------------------------------------------------------------------
>
> Key: MNG-2553
> URL: http://jira.codehaus.org/browse/MNG-2553
> Project: Maven 2
> Issue Type: Improvement
> Components: Settings
> Affects Versions: 2.0.4
> Reporter: Jimisola Laursen
> Fix For: 3.x
>
>
> 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 contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
