[
http://jira.codehaus.org/browse/MRELEASE-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=134674#action_134674
]
PeteJohlie commented on MRELEASE-342:
-------------------------------------
And another thing, why is release:prepare actually checking stuff in, even if
there are failures?
"Convention Over Configuration" is only valuable if the conventions approach
reasonableness.
Based on my experience with Maven so far, it seems to be a cover for poorly
written code.
So now the "configuration" I will have to do is to create a custom plugin.
There is no mechanism for moving an artifact up a release path.
Seems like a standard process: develop something, deploy it to a test server,
approve it, tag it as a release, and deploy it to a respository and stage
server (manually pick that up for production release).
Thre are so many assumptions built into the "conventions" that are not always
applicable and should have been configurable. It would have been acceptable if
the conventions were in fact merely pre-selected configurations that could be
overridden. But they are locked in.
> 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: http://jira.codehaus.org/browse/MRELEASE-342
> Project: Maven 2.x Release Plugin
> Issue Type: Wish
> Components: scm
> Reporter: PeteJohlie
>
> 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.
-
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
