jira-importer commented on issue #744: URL: https://github.com/apache/maven-scm/issues/744#issuecomment-2964617925
**[João Rafael Nicola](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=joaoraf)** commented I am also experiencing a similar effect. My parent pom has, for example: \<developerConnection>scm:svn:https://svnserver/myprojects/${project.artifactId}/trunk\</developerConnection> When running "mvn help:effective-pom" on the child, whose artifactId is, for example, child-project, I get: \<developerConnection>scm:svn:https://svnserver/myprojects/child-project/trunk/child-project\</developerConnection> instead of the expected: \<developerConnection>scm:svn:https://svnserver/myprojects/child-project/trunk\</developerConnection> For some reason, the developerConnection property gets appended with the artifactId when inherited. Although this makes sense when dealing with a multi-module project which is versioned in a single project structure in subversion, it does not when the parent pom is used just to standardize some properties on the pom, which each child project independently versioned. I think there should be some way to disable this behaviour. João Nicola -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
