jira-importer commented on issue #494: URL: https://github.com/apache/maven-scm/issues/494#issuecomment-2964598915
**[Jason Melnick](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jmaelstrom)** commented I looked for an existing against SCM, but didn't find one - although there may be one for M2 in general. Another observation: An inherited SCM URL assumes the svn path is inheritance based as well - for example: SCM info in BasePOM as: \<url>https://{removed}/trunk/m2_refapp/BasePOM\</url> A child of BasePOM called ProjectPOM would then have it's scm url interpreted as: \<url>https://{removed}/trunk/m2_refapp/BasePOM/ProjectPOM\</url> And likewise a child of ProjectPOM called ArtifactPOM would have an interpreted url as such: \<url>https://{removed}/trunk/m2_refapp/BasePOM/ProjectPOM/ArtifactPOM\</url> I'm thinking that these issues could be resolved by adding the following configuration options: String defaultLocation - The location, relative to the scm base url, of this project. boolean autoResolve - If true it would locate the svn project based on the way it currently works (but taking into account the new defaultLocation config option. If false it would just use the base scm url and append either the artifactId (by default) or the provided defaultLocation option. I'm sure that it's not that simple under the covers, but I do think that this would provide the flexibility that is necessary. -- 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]
