[
https://issues.apache.org/jira/browse/SCM-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963168#comment-17963168
]
ASF GitHub Bot commented on SCM-800:
------------------------------------
jira-importer commented on issue #1030:
URL: https://github.com/apache/maven-scm/issues/1030#issuecomment-2964639963
**[Rami
Ojares](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rojares)**
commented
First of all even if I would use multi module function of maven the pom
parent pom is orthogonal to module parent. What I mean with this fancy word is
that choosing the parent pom is independent of choosing the module hierarchy.
Go read any maven book and that's what they tell you. You could inherit the pom
from your module parent but not necessarily.
Secondly you don't have to organize your module hierarchy so that modules
are always directly under the parent module. I remember reading about a flat
hierarchy where they are siblings.
Finally I am not asking a change that would break backward compatibility. I
am not asking that adding the artifactId would be removed completely. I am
merely asking that this undocumented and unexpected convention could be
circumvented somehow.
> scm connection, developerConnection and url add artifactId at the end when
> they are inherited.
> ----------------------------------------------------------------------------------------------
>
> Key: SCM-800
> URL: https://issues.apache.org/jira/browse/SCM-800
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-plugin
> Affects Versions: 1.9.4
> Environment: All environments
> Reporter: Rami Ojares
> Priority: Major
>
> This issue is pretty much explained in the summary.
> scm fragment can not be inherited in most cases because the system adds
> child's artifactId always at the end of the project. Adding it automatically
> is of course nice for those few project's where the parent pom happens to be
> in the parent folder. But for everyone else it's a showstopper.
> This seems to affect also some other urls/paths and this issue has been
> reported in one way or another numerous times since 2006. It's about time to
> fix it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
