[
https://issues.apache.org/jira/browse/SCM-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960432#comment-17960432
]
ASF GitHub Bot commented on SCM-129:
------------------------------------
jira-importer commented on issue #401:
URL: https://github.com/apache/maven-scm/issues/401#issuecomment-2964591914
**[Dennis
Lundberg](https://issues.apache.org/jira/secure/[email protected])**
commented
I believe that this has been fixed by SCM-125. I will try to set up my
dependencies on a project, to use the latest snapshots and see if I can get it
to work.
> maven-release-plugin's checkForLocalModifications fails when there is non scm
> files the project
> -----------------------------------------------------------------------------------------------
>
> Key: SCM-129
> URL: https://issues.apache.org/jira/browse/SCM-129
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-cvs
> Affects Versions: 1.0-beta-3
> Environment: xp, cvs, latest maven-release-snapshot snaphot
> Reporter: Dan Tran
> Priority: Major
>
> when there are local files ( non scm files ) in the project, it becomes
> unknow files when release plugin perform scm:status
> and there for release:prepare will fail.
> Is there a way for cvs provider to ignore those files so that release plugin
> will be happy?
> The word around is to do a clean checkout before release:prepare.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
