[
https://issues.apache.org/jira/browse/SCM-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694843#comment-14694843
]
Hervé Boutemy commented on SCM-800:
-----------------------------------
FYI, I'm working on better documenting this convention 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
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
> Issue Type: Bug
> Components: maven-plugin
> Affects Versions: 1.9.4
> Environment: All environments
> Reporter: Rami Ojares
> Fix For: 1.9.5
>
>
> 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
(v6.3.4#6332)
