You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Bernd (JIRA)" <ji...@codehaus.org> on 2007/01/11 15:36:21 UTC
[jira] Created: (SCM-270) scm:update does not set
revisionKey/scm.property
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
[jira] Commented: (SCM-270) scm:update does not set
revisionKey/scm.property
Posted by "Bernd (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-270?page=comments#action_84879 ]
Bernd commented on SCM-270:
---------------------------
could it be that this is a more general issue with my german svn installation:
Running org.apache.maven.scm.provider.svn.svnexe.command.status.SvnExeStatusCommandTckTest
Test command line: svnadmin create repository
[INFO] Executing: svn --non-interactive checkout file:///D:/maven/maven-scm-provider-svnexe/target/scm-test/repository/trunk working-copy
[INFO] Working directory: D:\maven\maven-scm-provider-svnexe\target\scm-test
[INFO] Executing: svn --non-interactive checkout file:///D:/maven/maven-scm-provider-svnexe/target/scm-test/repository/trunk updating-copy
[INFO] Working directory: D:\maven\maven-scm-provider-svnexe\target\scm-test
[INFO] Executing: svn add --non-recursive project.xml
[INFO] Working directory: D:\maven\maven-scm-provider-svnexe\target\scm-test\working-copy
[INFO] Executing: svn --non-interactive commit --file C:\DOKUME~1\bep\LOKALE~1\Temp\maven-scm-1299438067.commit
[INFO] Working directory: D:\maven\maven-scm-provider-svnexe\target\scm-test\working-copy
[INFO] Unknown line: 'Hinzuf?gen project.xml'
[INFO] Unknown line: 'Sende readme.txt'
[INFO] Unknown line: 'Übertrage Daten ..'
[INFO] Unknown line: 'Revision 9 ?bertragen.'
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.886 sec <<< FAILURE!
> 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
[jira] Commented: (SCM-270) scm:update does not set
revisionKey/scm.property
Posted by "Bernd (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (SCM-270) scm:update does not set
revisionKey/scm.property
Posted by "Bernd (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-270?page=comments#action_84883 ]
Bernd commented on SCM-270:
---------------------------
Forcing my svn installation to english resolves the issue. It also makes the tests pass.
> 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
[jira] Commented: (SCM-270) scm:update does not set
revisionKey/scm.property
Posted by "Bernd (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-270?page=comments#action_84869 ]
Bernd commented on SCM-270:
---------------------------
This is the output from the command line:
D:\xx\>svn --username maven --non-interactive update
Revision 380.
org.apache.maven.scm.provider.svn.svnexe.command.update.SvnUpdateConsumer
contains
private static final String AT_REVISION_TOKEN = "At revision";
..
else if ( line.startsWith( AT_REVISION_TOKEN ) )
{
String revisionString = line.substring( AT_REVISION_TOKEN.length() + 1, line.length() - 1 );
revision = parseInt( revisionString );
so line.startsWith( AT_REVISION_TOKEN ) ) most likely does not compare sucessfully.
> 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
[jira] Closed: (SCM-270) scm:update does not set
revisionKey/scm.property
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Venisse closed SCM-270.
--------------------------------
Assignee: Emmanuel Venisse
Resolution: Won't Fix
We support only english parsing
> 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
> Assigned To: Emmanuel Venisse
>
> 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