[MRELEASE-1137] git path suffix from submodule

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 3.0.1
• Assignee: Unassigned
• Reporter: Rüdiger zu Dohna
• Created: 17/Jan/24 13:42
• Updated: 01/Jul/24 11:44
• Resolved: 01/Jul/24 11:44

Description

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

Issue Links

• duplicates: MRELEASE-942 scm.url in release.properties incorrectly has project name appended if not defined in the top level pom