[
https://jira.codehaus.org/browse/MRELEASE-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=334275#comment-334275
]
Emilio Jose Mena Cebrian commented on MRELEASE-798:
---------------------------------------------------
I know it, but it's a workaround until your solution is available.
I had to implement it for my company and i thought it might help Thorsten
Hoeger
A better solution might be to have a extension point to modify files and add
them to the commit as you said.
So a "ModifyFilesForDevelopmentPhase" runs every extension to modify files and
"register" changes to a "ChangedFilesManager"
That ChangedFilesManager might save previous version of modified files in case
you have to restore them (e.g.: a rollback)
So RewritePomsFor*Phase classes might be a implementation of this extension and
ScmCommit*Phase classes might commit only files registered in
"ChangedFilesManager" and not only poms.
What do you think about it?
> 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
