[
https://jira.codehaus.org/browse/MRELEASE-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MRELEASE-342.
---------------------------------
Resolution: Duplicate
Assignee: Brett Porter
> Can I get release plugin to not modify trunk pom's scm/connection and scm/url
> elements during prepare/perform? (version ok to modify)
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-342
> URL: https://jira.codehaus.org/browse/MRELEASE-342
> Project: Maven 2.x Release Plugin
> Issue Type: Wish
> Components: scm
> Reporter: PeteJohlie
> Assignee: Brett Porter
>
> We are using eclipse, subversion, maven, jboss, and continuum on linux. After
> button-push in continuum is moving our snapshots to a tag, we use
> cargo:deploy to put them in jboss (4.0.2).
> We number like this:
> 1.0.0.1-SNAPSHOT.war, on dev machine for continuous integration
> 1.0.0.1.war , on tst machine for QAT
> and we would like
> 2.0.0.0.war , on stg/prd machine for final version.
> I have modified the trunk/pom.xml to use variables for "branch". So when we
> want to cut a stg/prd release, we just point to an already tagged and tested
> incremental "release" from tst. The only problem is that the trunk/pom.xml's
> scm/connection and scm/url elements are getting overridden during the
> release/prepare step. the variables are being removed and the values derived
> during the goal are inserted.
> Is there a way to "control" how much of the trunk/pom.xml get's re-written? I
> understand the rewriting of the version element, but not the other scm
> elements.
> Any ideas would be appreciated.
> Thanks
> Pete
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
