[ 
https://issues.apache.org/jira/browse/SCM-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694223#comment-14694223
 ] 

Hervé Boutemy commented on SCM-800:
-----------------------------------

ok, I see
if your artifact is the root of a multi-module project, it will be normal to 
add module artifact-ids at end

but I understand that every project has a specific location in svn: Maven can't 
imagine your personal (very specific) conventions
then you'll have to explicitely configure each project

perhaps you're in the special case where you never have any multi-module 
project, then you expect a parent with $\{project.artifactId} will implement 
your specific convention: I understand that this very limited use-case is 
broken by automatic artifactId addition, but since this is a very limited 
use-case, ie you can't have multi-module project, I don't see this as really 
valid

> 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)

Reply via email to