[
http://jira.codehaus.org/browse/SCM-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190123#action_190123
]
Martin Scholl commented on SCM-480:
-----------------------------------
Same here:
Mac OSX 10.5.8
Maven 2.2.1
Subversion 1.6.5
JDK 1.6.0_15
svn status shows modified files but scm:check-local-modification won't fail due
to invalid scm:status behaviour.
$ svn status
M pom.xml
$ mvn scm:check-local-modification
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'scm'.
[INFO] ------------------------------------------------------------------------
[INFO] Building global parent POM
[INFO] task-segment: [scm:check-local-modification]
[INFO] ------------------------------------------------------------------------
[INFO] [scm:check-local-modification {execution: default-cli}]
[INFO] Executing: /bin/sh -c cd
/Users/mscholl/svnwork/central/de/cismet/global-parent/trunk && svn
--non-interactive status
[INFO] Working directory:
/Users/mscholl/svnwork/central/de/cismet/global-parent/trunk
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3 seconds
[INFO] Finished at: Mon Sep 07 18:16:49 CEST 2009
[INFO] Final Memory: 13M/80M
[INFO] ------------------------------------------------------------------------
Unfortunately the 1.3-SNAPSHOT build doesn't fix that (at the moment). Is there
a chance that it will be fixed in the near future?
> "mvn scm:status" doesn't show modified file
> -------------------------------------------
>
> Key: SCM-480
> URL: http://jira.codehaus.org/browse/SCM-480
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
> Affects Versions: 1.2
> Environment: OS X 10.5.7
> JDK 1.5
> Maven 2.1.0
> SVN 1.6.2
> Reporter: Victor Volle
>
> "svn status" gives
> M src/main/java/de/artive/test/FooBar.java
> "mvn scm:status" gives
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'scm'.
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building test-build
> [INFO] task-segment: [scm:status] (aggregator-style)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] [scm:status]
> [INFO] Executing: /bin/sh -c cd /Users/vivo/workspaces/eclipse-3.4/test-build
> && svn --username vivo --password '*****' --non-interactive status
> [INFO] Working directory: /Users/vivo/workspaces/eclipse-3.4/test-build
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 4 seconds
> [INFO] Finished at: Fri Jun 26 13:01:04 CEST 2009
> [INFO] Final Memory: 15M/29M
> [INFO]
> ------------------------------------------------------------------------
> The changed file is not shown.
> This wouldn't be that bad, if the the release plugin therefore would not
> recognize that there still is a modified file in the workspace
--
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
