[
https://issues.apache.org/jira/browse/SCM-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964854#comment-17964854
]
Olivier Lamy commented on SCM-751:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#957|https://github.com/apache/maven-scm/issues/957].
> SCM child-project URL composition issue
> ---------------------------------------
>
> Key: SCM-751
> URL: https://issues.apache.org/jira/browse/SCM-751
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 1.9, 1.9.1
> Environment: Maven 3.0.5 (because of other restrictions I'm unable to
> upgrade), Windows, Mac, Git 1.8.4 & Git 1.9.2
> Reporter: JCC Van Andel
> Priority: Major
>
> Hi,
> I've migrated some projects from SVN to Git and removed all the SCM entries
> from all but the parent pom.xml. This sounded valid, as the SCM URL will be
> the same for all modules (same Git repo).
> But releasing a sub module (I release submodules separately, not as part of a
> multi-module build) causes the SCM URLs to get the modulename appended, like
> this.
> Original, configured URL: https://git......nl/scm/on/repo.git
> URL used to push: https://git......nl/scm/on/repo.git/modulename
> I found this discussion from 2011:
> http://mail-archives.apache.org/mod_mbox/maven-dev/201107.mbox/%[email protected]%3E
> But I don't see any way in how this is currently resolved. Is this still an
> open issue?
> I'm able to add SCM tags to every module, but that seems a bit cumbersome. Is
> there another way around this?
> Cheers,
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
