[
https://issues.apache.org/jira/browse/SCM-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963165#comment-17963165
]
ASF GitHub Bot commented on SCM-800:
------------------------------------
jira-importer commented on issue #1030:
URL: https://github.com/apache/maven-scm/issues/1030#issuecomment-2964639954
**[Hervé
Boutemy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hboutemy)**
commented
ok, I see the idea: adding an attribute to POM (with a better name to be
found ;) ), then the chang will be in Maven core, hence MNG Jira project
notice that this attribute should be inherited too, since I suppose the
child of a child should have the same value
I'll keep this as an option
My current favorite is to check for every supported scm that scm urls
support adding path, since this info can be useful even for SCMs that only
support repo, not path inside repo
Notice that urls for connection/developerCOnnection is
scm:\<provider>:provider-specific-content
then we can improve the url if it doesn't match our expectations
I'll probably need help to complete the check for every scm: I'll report
here to ask for help
> 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)
