[
https://issues.apache.org/jira/browse/SCM-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14692948#comment-14692948
]
Rami Ojares edited comment on SCM-800 at 8/12/15 5:43 AM:
----------------------------------------------------------
I don't completely understand your preferred idea.
But anything is fine with me as long as maven does not append any extra path
components in my case. Just to make sure let me elaborate on that one.
Here is my url again in the parent pom:
{code}
/url/to/subversion/repo/$\{category}/$\{articactId}/$\{path_to_branch}
{code}
When the child inherits this it uses it's own property values and automatically
the path is correct. Even though subversion repositories do use paths for
everything I simply do not want the system to append always the artifactId
because it does not match the project layout in my repository.
was (Author: rojares):
I don't completely understand your preferred idea.
But anything is fine with me as long as maven does not append any extra path
components in my case. Just to make sure let me elaborate on that one.
Here is my url again in the parent pom:
{code}
/url/to/subversion/repo/${category}/${articactId}/${path_to_branch}
{/code}
When the child inherits this it uses it's own property values and automatically
the path is correct. Even though subversion repositories do use paths for
everything I simply do not want the system to append always the artifactId
because it does not match the project layout in my repository.
> 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)
