[
https://issues.apache.org/jira/browse/MRELEASE-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16221533#comment-16221533
]
ASF GitHub Bot commented on MRELEASE-798:
-----------------------------------------
ctubbsii commented on issue #4: [MRELEASE-798] Commit additional files with
release plugin
URL: https://github.com/apache/maven-release/pull/4#issuecomment-339842030
+1 to this feature request
I'm trying to update an OSGi manifest with the version derived from the
version in the pom.xml. The build will fail if they do not match, which means I
must do manual releases and cannot use the maven-release-plugin. This is
unfortunate.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Commit additional files with release plugin
> -------------------------------------------
>
> Key: MRELEASE-798
> URL: https://issues.apache.org/jira/browse/MRELEASE-798
> Project: Maven Release Plugin
> Issue Type: Improvement
> Components: prepare, scm
> Affects Versions: 2.3.2
> Reporter: Thorsten Hoeger
> Labels: github-pullrequest
> 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 was sent by Atlassian JIRA
(v6.4.14#64029)
