[jira] [Commented] (MNG-5870) Effective pom should not inherit SCM

["Robert Scholte (JIRA)" <ji...@apache.org>]

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

Robert Scholte commented on MNG-5870:
-------------------------------------

My ideal proposal would be that the build pom would have no scm, but the consumer pom does. While creating the consumer pom it should ask its scm tool for the repo path, possible extended with a separate path to the module folder. If we can make it independent from the scm-tool, then we could define a scm2-protocol which is controlled by Maven and not by any SCM provider. 

> Effective pom should not inherit SCM
> ------------------------------------
>
>                 Key: MNG-5870
>                 URL: https://issues.apache.org/jira/browse/MNG-5870
>             Project: Maven
>          Issue Type: Improvement
>          Components: core, Inheritance and Interpolation, POM
>            Reporter: Robert Scholte
>            Priority: Major
>
> Up until Maven 3.3.7 if a pom didn't specify the scm section, it would be inherited and extended with the artifactId *by default*. This mechanism could work for a couple of SCMs like svn and cvs, but for most it doesn't.
> This kind of scm specific logic of extending the connection or URL doesn't belong in Maven core. 
> Instead we should say that scm marks this project as a valid release root. 
> The source repository page (mpir) should ask a specific Scm class for handling connections and urls in case of modules.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)