[
https://issues.apache.org/jira/browse/SCM-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960591#comment-17960591
]
ASF GitHub Bot commented on SCM-190:
------------------------------------
jira-importer commented on issue #429:
URL: https://github.com/apache/maven-scm/issues/429#issuecomment-2964594010
**[Eric
Bernstein](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ebernstein)**
commented
The .scm directory doesn't seem all that bad - esp given that it's shared
across projects.
Is there anything that needs to be done to expedite the scm release? My
company's cvs will actually hang when using compression - which is another
issue entirely, but having a good way to configure that would be incredibly
useful. If there are tasks that need to be done before scm can be released I'm
sure I can find some cycles to help out. Let me know if there's anything I can
do to get this out sooner. Thanks.
> Location of cvs-settings.xml should be in user.home and not in user.dir
> -----------------------------------------------------------------------
>
> Key: SCM-190
> URL: https://issues.apache.org/jira/browse/SCM-190
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-cvs
> Affects Versions: 1.0-beta-3
> Reporter: Thibaut CAZENAVE
> Assignee: Emmanuel Venisse
> Priority: Trivial
> Fix For: 1.0-beta-4
>
>
> In static method getSettings() of CvsUtil class
> (org.apache.maven.scm.provider.cvslib.util), we try to get the
> cvs-settings.xml property file from ${user.dir}/.scm/
> ------------------------------------
> File scmUserDir = new File( System.getProperty( "user.dir" ), ".scm" );
> File settingsFile = new File( scmUserDir, "cvs-settings.xml" );
> ------------------------------------
> The SCM documentation (http://maven.apache.org/scm/cvs.html) say this file
> should be in ${user.home}/.scm/ and not {user.dir}/.scm/.
> This should be easy to correct.
> Thibaut
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
