maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rami Ojares (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SCM-800) scm connection, developerConnection and url add artifactId at the end when they are inherited.
Date Tue, 11 Aug 2015 08:11:46 GMT

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

Rami Ojares commented on SCM-800:
---------------------------------

I readily admit that I do not know Maven source code.
I comment here merely as a user.
Fixing for me would mean minimally the following.

Parent:
<scm doNotAppendArtifactIdAtTheEndOfTheUrl="true">
    <developerConnection>protocol://host/path</developerConnection>
</scm>

Child that does not define scm, would have the following effective pom
<scm>
    <developerConnection>protocol://host/path</developerConnection>
</scm>

Notice: Child's artifactId is NOT appended at the end of the path.

This attribute would remove the appending of artifactId also to connection and url tags.
And if this same issue is plaguing other tags (like site related tags) then let's apply the
same strategy there.


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

Mime
View raw message