[ http://jira.codehaus.org/browse/SCM-129?page=comments#action_55190 ]
Dan Tran commented on SCM-129: ------------------------------ I guess you can open jira against m2 release plugin. There is a similar JIRA for m2 release plugin already. In my case, I happen to have other none scm files unrelated to the build and release plugin is not happy about after SCM 125 fix. I think maven scm for scv provide should quietly ignore "?" status and not report as unknown > maven-release-plugin's checkForLocalModifications fails when there is non scm > files the project > ----------------------------------------------------------------------------------------------- > > Key: SCM-129 > URL: http://jira.codehaus.org/browse/SCM-129 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-cvs > Versions: 1.0-beta-3 > Environment: xp, cvs, latest maven-release-snapshot snaphot > Reporter: Dan Tran > Fix For: 1.0-beta-3 > > > 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 is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira