You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/19 15:53:00 UTC

[jira] [Closed] (MRELEASE-962) A way for other plugins to hook into the release and add files to SCM

     [ https://issues.apache.org/jira/browse/MRELEASE-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliotte Rusty Harold closed MRELEASE-962.
------------------------------------------

> A way for other plugins to hook into the release and add files to SCM
> ---------------------------------------------------------------------
>
>                 Key: MRELEASE-962
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-962
>             Project: Maven Release Plugin
>          Issue Type: Wish
>          Components: prepare
>            Reporter: Kasper Sørensen
>            Priority: Major
>
> Hi Maven Release community,
> I am working on a plugin for driving dotnet (.NET core) builds via Maven [1]. One particularly annoying thing with such projects is that project versions have to be sync'ed manually, while I would like it to be something that is governed by Maven so that if the pom.xml file specifies a version, then that is propagated also to the project.json files of a dotnet build/release. My plugin now has a goal for doing this (dotnet:update-versions) but I cannot hook that into the release process so that the outcome of this step (the changed project.json files) are added to the commits made by the release plugin. I have looked around in your source code and cannot find any way of doing it, and I also see that the release plugin explicitly only adds pom.xml files to the commit. Having a way to add other files would be great.
> [1] https://github.com/kaspersorensen/dotnet-maven-plugin



--
This message was sent by Atlassian Jira
(v8.3.4#803005)