You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2018/03/16 22:42:04 UTC

[jira] [Closed] (MRELEASE-898) release:branch fails in a multi-project git project with each project in its own repository.

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

Michael Osipov closed MRELEASE-898.
-----------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

> release:branch fails in a multi-project git project with each project in its own repository.
> --------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-898
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-898
>             Project: Maven Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.5.1
>            Reporter: Ralph Goers
>            Priority: Major
>         Attachments: maven.log, releasetest.zip
>
>
> I have a sample project that illustrates how our project is organized - every project is in its own git repo. When trying to perform a release:branch on this project it fails to add the modified poms because it tries to perform a git add on all of them at once.  This fails with a message saying a pom is outside the repository.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)