[
https://issues.apache.org/jira/browse/MRELEASE-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17861114#comment-17861114
]
Edoardo Causarano edited comment on MRELEASE-1137 at 7/1/24 11:04 AM:
----------------------------------------------------------------------
Looks like a duplicate of [MRELEASE-942] and [MRELEASE-885]
was (Author: ecausarano):
Looks like a duplicate of https://issues.apache.org/jira/browse/MRELEASE-942
> git path suffix from submodule
> ------------------------------
>
> Key: MRELEASE-1137
> URL: https://issues.apache.org/jira/browse/MRELEASE-1137
> Project: Maven Release Plugin
> Issue Type: Bug
> Affects Versions: 3.0.1
> Reporter: Rüdiger zu Dohna
> Priority: Major
>
> We have a mono-repo with a root maven pom and submodules that we want to
> release independently. But when we run the release plugin on the submodule,
> it logs:
> {{[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:3.0.1:prepare (default-cli) on
> project {_}submodule{_}: Unable to commit files}}
> {{[ERROR] Provider message:}}
> {{[ERROR] The git-push command failed.}}
> {{[ERROR] Command output:}}
> {{[ERROR] Gitea: Invalid repo name}}
> {{[ERROR] fatal: Could not read from remote repository.}}
> {{[ERROR] }}
> {{[ERROR] Please make sure you have the correct access rights}}
> {{[ERROR] and the repository exists.}}
> It tries to access the repository {{{}{_}monorepo{_}.git/{_}submodule{_}{}}},
> even though the {{scm}} tag is only defined in the parent pom (without the
> submodule path).
> If we copy the exact same {{scm}} tag to the submodules pom, it works just
> fine.
> We found the same issue as an unanswered question on Stackoverflow:
> [https://stackoverflow.com/questions/64588882/maven-release-plugin-for-project-submodules]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
