[
https://issues.apache.org/jira/browse/SCM-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963169#comment-17963169
]
ASF GitHub Bot commented on SCM-800:
------------------------------------
jira-importer commented on issue #1030:
URL: https://github.com/apache/maven-scm/issues/1030#issuecomment-2964639964
**[Hervé
Boutemy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hboutemy)**
commented
FYI, I'm working on better documenting this convention (see
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commitdiff;h=33de19713387e37bd371465e52278aedd5ad0ffd
) and preparing for future enhancements (whatever they may be): see MNG-5871
I understand that "multi module function of maven the pom parent pom is
orthogonal to module parent": but the algorithm for extrapolating child value
from parent value is the same, since there is only one inheritance. And adding
${project.artifactId} in a parent pom will cause issues when used in child of a
child, since the result won't be what you expect: the issue is not caused by
inheritance but parameter interpolation that happens at the end, then the value
is always the value of the current pom (see
https://stackoverflow.com/questions/20513744/project-artifactid-in-parent-pom-xml-resolves-odd/20517630#20517630
)
this will probably take some time to make everybody ok on a solution (and
make sure everybody understands impacts of any change): but we are going
forward, we just need to stay patient and continue positive discussions
> 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)
