You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (JIRA)" <ji...@codehaus.org> on 2014/05/11 19:23:10 UTC
[jira] (SCM-392) SCM SVN plugin does not cope with a flat structure
[ https://jira.codehaus.org/browse/SCM-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy updated SCM-392:
------------------------------
Description:
All of this is when using a flat (eclipse based) directory structure.
When performing a release, the release plugin correctly modifies the pom.xml files (so it finds them), however, when attempting to check in the changes, SVN complains that the workspace directory (the one immediately above all of the flat projects) is not under SVN control - which it isn't and should not be.
I've created a public svn repo that you can get to and test against:
http://svn.warpspeed.com.au/test-repos/
everything that you need is in there.
The final output is:
{noformat} [INFO]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] ------------------------------------------------------------------------
[INFO] FireDragon - J2EE Multi Module Project ................ SUCCESS [9.687s]
[INFO] FireDragon - Resources Project ........................ SUCCESS [3.094s]
[INFO] FireDragon - WAR Project .............................. SUCCESS [5.500s]
[INFO] FireDragon - EAR Project .............................. SUCCESS [2.891s]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 31 seconds
[INFO] Finished at: Wed Jul 16 02:12:04 GMT 2008
[INFO] Final Memory: 21M/38M
[INFO] Checking in modified POMs...
[INFO] ------------------------------------------------------------------------
[INFO] Executing: svn --non-interactive commit --file C:\Temp\maven-scm-1721327855.commit --targets C:\Temp\maven-scm-21219-targets
[INFO] Working directory: C:\WorkSpaces\SCMTest\FireDragon
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
svn: 'C:\WorkSpaces\SCMTest' is not a working copy
svn: Can't open file 'C:\WorkSpaces\SCMTest\.svn\entries': The system cannot find the path specified.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2 minutes 33 seconds
[INFO] Finished at: Wed Jul 16 02:13:48 GMT 2008
[INFO] Final Memory: 6M/12M
[INFO] ------------------------------------------------------------------------{noformat}
where DIR C:\WorkSpaces\SCMTest is:
{noformat} Volume in drive C has no label.
Volume Serial Number is 201B-748A
Directory of C:\WorkSpaces\SCMTest
16/07/2008 12:03 PM <DIR> .
16/07/2008 12:03 PM <DIR> ..
16/07/2008 11:41 AM <DIR> .metadata
16/07/2008 12:00 PM <DIR> FireDragon
16/07/2008 12:00 PM <DIR> FireDragonEAR
16/07/2008 12:00 PM <DIR> FireDragonResources
16/07/2008 12:00 PM <DIR> FireDragonWeb
16/07/2008 11:03 AM <DIR> warpspeed-build-tools
16/07/2008 10:53 AM <DIR> warpspeed-dynamic-parent
16/07/2008 10:50 AM <DIR> warpspeed-parent
0 File(s) 0 bytes
10 Dir(s) 1,889,746,944 bytes free{noformat}
The file maven-scm-1721327855.commit, contains:
{noformat}[maven-release-plugin] prepare release FireDragon-1.0.5
The file maven-scm-21219-targets, contains:
C:/WorkSpaces/SCMTest/FireDragon/pom.xml
C:/WorkSpaces/SCMTest/FireDragonResources/pom.xml
C:/WorkSpaces/SCMTest/FireDragonWeb/pom.xml
C:/WorkSpaces/SCMTest/FireDragonEAR/pom.xml
{noformat}
(which appears to be all correct)
was:
All of this is when using a flat (eclipse based) directory structure.
When performing a release, the release plugin correctly modifies the pom.xml files (so it finds them), however, when attempting to check in the changes, SVN complains that the workspace directory (the one immediately above all of the flat projects) is not under SVN control - which it isn't and should not be.
I've created a public svn repo that you can get to and test against:
http://svn.warpspeed.com.au/test-repos/
everything that you need is in there.
The final output is:
[INFO]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] ------------------------------------------------------------------------
[INFO] FireDragon - J2EE Multi Module Project ................ SUCCESS [9.687s]
[INFO] FireDragon - Resources Project ........................ SUCCESS [3.094s]
[INFO] FireDragon - WAR Project .............................. SUCCESS [5.500s]
[INFO] FireDragon - EAR Project .............................. SUCCESS [2.891s]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 31 seconds
[INFO] Finished at: Wed Jul 16 02:12:04 GMT 2008
[INFO] Final Memory: 21M/38M
[INFO] Checking in modified POMs...
[INFO] ------------------------------------------------------------------------
[INFO] Executing: svn --non-interactive commit --file C:\Temp\maven-scm-1721327855.commit --targets C:\Temp\maven-scm-21219-targets
[INFO] Working directory: C:\WorkSpaces\SCMTest\FireDragon
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
svn: 'C:\WorkSpaces\SCMTest' is not a working copy
svn: Can't open file 'C:\WorkSpaces\SCMTest\.svn\entries': The system cannot find the path specified.
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2 minutes 33 seconds
[INFO] Finished at: Wed Jul 16 02:13:48 GMT 2008
[INFO] Final Memory: 6M/12M
[INFO] ------------------------------------------------------------------------
where DIR C:\WorkSpaces\SCMTest is:
Volume in drive C has no label.
Volume Serial Number is 201B-748A
Directory of C:\WorkSpaces\SCMTest
16/07/2008 12:03 PM <DIR> .
16/07/2008 12:03 PM <DIR> ..
16/07/2008 11:41 AM <DIR> .metadata
16/07/2008 12:00 PM <DIR> FireDragon
16/07/2008 12:00 PM <DIR> FireDragonEAR
16/07/2008 12:00 PM <DIR> FireDragonResources
16/07/2008 12:00 PM <DIR> FireDragonWeb
16/07/2008 11:03 AM <DIR> warpspeed-build-tools
16/07/2008 10:53 AM <DIR> warpspeed-dynamic-parent
16/07/2008 10:50 AM <DIR> warpspeed-parent
0 File(s) 0 bytes
10 Dir(s) 1,889,746,944 bytes free
The file maven-scm-1721327855.commit, contains:
[maven-release-plugin] prepare release FireDragon-1.0.5
The file maven-scm-21219-targets, contains:
C:/WorkSpaces/SCMTest/FireDragon/pom.xml
C:/WorkSpaces/SCMTest/FireDragonResources/pom.xml
C:/WorkSpaces/SCMTest/FireDragonWeb/pom.xml
C:/WorkSpaces/SCMTest/FireDragonEAR/pom.xml
(which appears to be all correct)
> SCM SVN plugin does not cope with a flat structure
> --------------------------------------------------
>
> Key: SCM-392
> URL: https://jira.codehaus.org/browse/SCM-392
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
> Environment: XP SP2, IBM Java 5, Sun SDJ 6.
> Reporter: Chris Graham
>
> All of this is when using a flat (eclipse based) directory structure.
> When performing a release, the release plugin correctly modifies the pom.xml files (so it finds them), however, when attempting to check in the changes, SVN complains that the workspace directory (the one immediately above all of the flat projects) is not under SVN control - which it isn't and should not be.
> I've created a public svn repo that you can get to and test against:
> http://svn.warpspeed.com.au/test-repos/
> everything that you need is in there.
> The final output is:
> {noformat} [INFO]
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO] ------------------------------------------------------------------------
> [INFO] FireDragon - J2EE Multi Module Project ................ SUCCESS [9.687s]
> [INFO] FireDragon - Resources Project ........................ SUCCESS [3.094s]
> [INFO] FireDragon - WAR Project .............................. SUCCESS [5.500s]
> [INFO] FireDragon - EAR Project .............................. SUCCESS [2.891s]
> [INFO] ------------------------------------------------------------------------
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 31 seconds
> [INFO] Finished at: Wed Jul 16 02:12:04 GMT 2008
> [INFO] Final Memory: 21M/38M
> [INFO] Checking in modified POMs...
> [INFO] ------------------------------------------------------------------------
> [INFO] Executing: svn --non-interactive commit --file C:\Temp\maven-scm-1721327855.commit --targets C:\Temp\maven-scm-21219-targets
> [INFO] Working directory: C:\WorkSpaces\SCMTest\FireDragon
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Unable to commit files
> Provider message:
> The svn command failed.
> Command output:
> svn: 'C:\WorkSpaces\SCMTest' is not a working copy
> svn: Can't open file 'C:\WorkSpaces\SCMTest\.svn\entries': The system cannot find the path specified.
> [INFO] ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 2 minutes 33 seconds
> [INFO] Finished at: Wed Jul 16 02:13:48 GMT 2008
> [INFO] Final Memory: 6M/12M
> [INFO] ------------------------------------------------------------------------{noformat}
> where DIR C:\WorkSpaces\SCMTest is:
> {noformat} Volume in drive C has no label.
> Volume Serial Number is 201B-748A
> Directory of C:\WorkSpaces\SCMTest
> 16/07/2008 12:03 PM <DIR> .
> 16/07/2008 12:03 PM <DIR> ..
> 16/07/2008 11:41 AM <DIR> .metadata
> 16/07/2008 12:00 PM <DIR> FireDragon
> 16/07/2008 12:00 PM <DIR> FireDragonEAR
> 16/07/2008 12:00 PM <DIR> FireDragonResources
> 16/07/2008 12:00 PM <DIR> FireDragonWeb
> 16/07/2008 11:03 AM <DIR> warpspeed-build-tools
> 16/07/2008 10:53 AM <DIR> warpspeed-dynamic-parent
> 16/07/2008 10:50 AM <DIR> warpspeed-parent
> 0 File(s) 0 bytes
> 10 Dir(s) 1,889,746,944 bytes free{noformat}
> The file maven-scm-1721327855.commit, contains:
> {noformat}[maven-release-plugin] prepare release FireDragon-1.0.5
> The file maven-scm-21219-targets, contains:
> C:/WorkSpaces/SCMTest/FireDragon/pom.xml
> C:/WorkSpaces/SCMTest/FireDragonResources/pom.xml
> C:/WorkSpaces/SCMTest/FireDragonWeb/pom.xml
> C:/WorkSpaces/SCMTest/FireDragonEAR/pom.xml
> {noformat}
> (which appears to be all correct)
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)