[
http://jira.codehaus.org/browse/MRELEASE-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=205204#action_205204
]
Trygve Laugstol commented on MRELEASE-184:
------------------------------------------
That's the obvious solution if you have the time to do it. It's actually still
relevant (even if my SCMs are supported) because the release plugin often fails
in fantastic ways.
The main point was that splitting up the quite big process into smaller parts
in one way or another would be nice as the parts are useful in itself. Imagine
for example a utility that tries to do automated updates of dependencies. For
such a utility a tool to (correctly) update a pom.xml file would be very useful.
> Ability to perform releases with unsupported SCMs
> -------------------------------------------------
>
> Key: MRELEASE-184
> URL: http://jira.codehaus.org/browse/MRELEASE-184
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Components: scm
> Reporter: Trygve Laugstol
>
> The current functionality of the release plugin is very useful, but requires
> that you use a supported SCM. It should be possible to change this
> requirement in (at least) two ways:
> o When doing the release process, pause and wait for the user to manually
> perform the steps that maven-scm normally would do, or
> o Break up the current monolitic goals into smaller parts so that the user
> can call them manually and to SCM operations in the background. I think this
> would be my approach, as there are several features of the release plugin
> that are useful outside of a release procedure context, the pom re-writing is
> the first that comes to mind.
--
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
