[SCM-800] scm connection, developerConnection and url add artifactId at the end when they are inherited.

**[Rami Ojares](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rojares)** opened **[SCM-800](https://issues.apache.org/jira/browse/SCM-800?redirect=false)** and commented

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.

---

**Affects:** 1.9.4

**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-5878](https://issues.apache.org/jira/browse/MNG-5878) add support for module name != artifactId in every calculated URLs (project, SCM, site): special project.directory property

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

1 votes, 4 watchers

The issue identifies inherited scm, developerConnection, and url handling in Maven POMs but names no source files or tests. Start by locating the code and tests that calculate inherited project URLs, then reproduce a parent/child POM case where the child artifactId is appended. Done means inherited paths remain usable without unwanted artifactId additions while intended relative paths still work.

Written by the indexing model from the issue text.