[
https://issues.apache.org/jira/browse/SCM-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961706#comment-17961706
]
ASF GitHub Bot commented on SCM-476:
------------------------------------
jira-importer commented on issue #693:
URL: https://github.com/apache/maven-scm/issues/693#issuecomment-2964613585
**[Michael
Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)**
commented
This issue has been auto closed because it has been inactive for a long
period of time. If you think this issue still applies, retest your problem with
the most recent version of Maven and the affected component, reopen and post
your results.
> Some help dealing with the fact that no two people will have their clones in
> the same location
> ----------------------------------------------------------------------------------------------
>
> Key: SCM-476
> URL: https://issues.apache.org/jira/browse/SCM-476
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-mercurial (hg)
> Affects Versions: 1.2
> Reporter: Benson Margulies
> Priority: Major
>
> It's not so easy to figure out what to put in a checked in POM with hg for
> the <scm/> element, since every developer is likely to keep his or her clone
> in a different location. Yes, you can put in a ${....} and expect each user
> to put something in their settings.xml to fill it in, but that seems rather
> complex. Really, the point is that "." is the right location. Right here,
> where the pom is sitting, is the important place. Couldn't the plugin default
> to just using the clone where it is?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
