You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2015/08/12 20:28:46 UTC

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

Robert Scholte created MNG-5870:
-----------------------------------

             Summary: 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


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
(v6.3.4#6332)