[
https://jira.codehaus.org/browse/MRELEASE-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=334338#comment-334338
]
Robert Scholte commented on MRELEASE-798:
-----------------------------------------
Since it's a workaround I'm not going to accept the pullrequest, because these
Maven plugins must stay backwards compatible. There's no such thing as a
temporary workaround, but users are free to use your fork of course.
I haven't collected all the requirements, but I think your idea is indeed a
good start. Very clever to think of the rollback as well.
> Commit additional files with release plugin
> -------------------------------------------
>
> Key: MRELEASE-798
> URL: https://jira.codehaus.org/browse/MRELEASE-798
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: prepare, scm
> Affects Versions: 2.3.2
> Reporter: Thorsten Hoeger
> Attachments: maven-release-2.4.1-additionalCommitted.patch
>
>
> Hi,
> is there any possibility to have the release-plugin commit additional files
> which were
> generated/modified in the preparationGoals.
> Now only the pom.xml is commited. Using scm-plugin has some serious drawbacks
> in this
> situation.
> If it is not possible at the moment, is there any chance to get this in the
> future. Maybe
> there could be a parameter additionalCommitFiles with a list of files to
> commit along with
> pom.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
