[ http://jira.codehaus.org/browse/SCM-270?page=comments#action_84882 ] Bernd commented on SCM-270: ---------------------------
here is the stacktrace for org.apache.maven.scm.provider.svn.svnexe.command.status.SvnExeStatusCommandTckTest junit.framework.AssertionFailedError: Expected 2 files in the committed files list [] expected:&2& but was:&0& at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:282) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:201) at org.apache.maven.scm.tck.command.status.StatusCommandTckTest.commit(StatusCommandTckTest.java:69) at org.apache.maven.scm.tck.command.status.StatusCommandTckTest.testStatusCommand(StatusCommandTckTest.java:97) > scm:update does not set revisionKey/scm.property > ------------------------------------------------ > > Key: SCM-270 > URL: http://jira.codehaus.org/browse/SCM-270 > Project: Maven SCM > Issue Type: Bug > Affects Versions: 1.0-beta-3 > Environment: Windows XP, Java(TM) 2 Runtime Environment, Standard > Edition (build 1.5.0_10-b03), > Reporter: Bernd > > Using > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-scm-plugin</artifactId> > <executions> > <execution> > <phase>validate</phase> > <id>getting-scm.revision</id> > <goals> > <goal>update</goal> > </goals> > </execution> > </executions> > </plugin> > as suggested on the user list results in > [INFO] [scm:update {execution: getting-scm.revision}] > [INFO] Executing: svn --username maven --non-interactive update > [INFO] Working directory: D:\projekte\template\templatePom-trunk > [DEBUG] Revision 375. > [INFO] Unknown file status: 'R' in line Revision 375.. > [INFO] Storing revision in 'scm.revision' project property. > This does not result in rev. 375 being replaced in filtered files. > Actual result is that the content of scm.revision is "0" > The filtered file looks like > xyz=0 > instead of the expteced > xyz=375 -- 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
