[MRELEASE-342] Can I get release plugin to not modify trunk pom's scm/connection and scm/url elements during prepare/perform? (version ok to modify)

• Type: Wish
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Component/s: scm
• Assignee: Brett Porter
• Reporter: PeteJohlie
• Created: 12/May/08 13:03
• Updated: 25/Jun/11 03:37
• Resolved: 25/Jun/11 03:36

Description

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

Issue Links

• duplicates: MRELEASE-128 SCM properties being replaced during release:perform