[MNG-5870] Effective pom should not inherit SCM

**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** opened **[MNG-5870](https://issues.apache.org/jira/browse/MNG-5870?redirect=false)** and commented

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.

---

**Issue Links:**
- [MPIR-234](https://issues.apache.org/jira/browse/MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

- [MNG-5951](https://issues.apache.org/jira/browse/MNG-5951) add an option to avoid path addition to inherited URLs
(_**"is superceded by"**_)

2 votes, 7 watchers