[
https://issues.apache.org/jira/browse/SCM-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959854#comment-17959854
]
ASF GitHub Bot commented on SCM-265:
------------------------------------
jira-importer commented on issue #255:
URL: https://github.com/apache/maven-scm/issues/255#issuecomment-2964581371
**[Dan
Batten](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=danatten)**
commented
The problem seems to stem from the fact that the maven-release-plugin still
references beta-3
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-release-plugin/2.0-beta-4/maven-release-plugin-2.0-beta-4.pom
When I changed this POM in my local repository to use beta-4 the problem
went away (a hack I know but I'm struggling to get release:perform to work).
> .scm/clearcase-settings.xml is read from current directory rather than the
> users home directory
> -----------------------------------------------------------------------------------------------
>
> Key: SCM-265
> URL: https://issues.apache.org/jira/browse/SCM-265
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-clearcase
> Affects Versions: 1.0-beta-4
> Reporter: Andreas Schildbach
> Assignee: Emmanuel Venisse
> Priority: Major
>
> I cannot say why, but on my Windows 2000 SP4 machine, the ClearCase-Provider
> searches for .scm/clearcase-settings.xml in the directory where I invoked
> mvn, rather than the users home directory as documented. This can be verified
> by using "filemon" from Sysinternals
> (http://www.microsoft.com/technet/sysinternals/utilities/filemon.mspx).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
