You are viewing a plain text version of this content. The canonical link for it is here.
Posted to scm-dev@maven.apache.org by ChrisGWarp <Ch...@aami.com.au> on 2008/07/13 09:06:01 UTC
Release/SCM broken for eclipse?
Hi all.
From what I can gather, the release plugin has been fixed to work with
the flattened eclipse based project structure.
But the results that I'm getting below tend to make me think that it is
the SCM plugin causing me the grief, and I cann't image that I'm doing
anything that out of the ordinary, so perhaps someone can point out what
I've done wrong.
I have 4 directories, all at the same level so that they work with
eclipse.
<workspace dir>\FireDragon (the J2EE Multi Module Build Project)
<workspace dir>\FireDragonResources (the resources project)
<workspace dir>\FireDragonWeb (the web/war project)
<workspace dir>\FireDragonEAR (the ear project).
The multi module build project has this in it:
<modules>
<module>../FireDragonResources</module>
<module>../FireDragonWeb</module>
<module>../FireDragonEAR</module>
</modules>
And each of the modules (Resources, WAR, EAR) have this as the parent:
<parent>
<groupId>au.com.warpspeed.firedragon</groupId>
<artifactId>FireDragon</artifactId>
<version>1.0.5-SNAPSHOT</version>
<relativePath>../FireDragon/pom.xml</relativePath>
</parent>
The project builds fine, so all of that is ok.
However, when I do a release:prepare, I get this as the final bit of the
output:
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
------------------------------------------------------------------------
[INFO] FireDragon - J2EE Multi Module Project ................
SUCCESS [13.125s]
[INFO] FireDragon - Resources Project ........................
SUCCESS [3.875s]
[INFO] FireDragon - WAR Project ..............................
SUCCESS [3:36.109s]
[INFO] FireDragon - EAR Project ..............................
SUCCESS [1:10.562s]
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 5 minutes 7 seconds
[INFO] Finished at: Sat Jul 12 21:38:26 EST 2008
[INFO] Final Memory: 19M/41M
[INFO]
------------------------------------------------------------------------
[INFO] Checking in modified POMs...
[INFO] Executing: svn --username chris --password ***** --non-interactive
commit --file C:\DOCUME~1\Chris\LOCALS~1\Temp\maven-scm-108910589.commi
t --targets C:\DOCUME~1\Chris\LOCALS~1\Temp\maven-scm-3540-targets
[INFO] Working directory: C:\Documents and Settings\Chris\My
Documents\IBM\rationalsdp7.0\workspace\FireDragon
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
svn: 'C:\Documents and Settings\Chris\My
Documents\IBM\rationalsdp7.0\workspace' is not a working copy
svn: Can't open file 'C:\Documents and Settings\Chris\My
Documents\IBM\rationalsdp7.0\workspace\.svn\entries': The system cannot find
the path specified.
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 5 minutes 24 seconds
[INFO] Finished at: Sat Jul 12 21:38:28 EST 2008
[INFO] Final Memory: 7M/13M
[INFO]
------------------------------------------------------------------------
Is the release plugin not really fixed (as claimed since beta-6 and I'm
using beta-8) or have I done something else that is wrong?
-Chris
--
View this message in context: http://www.nabble.com/Release-SCM-broken-for-eclipse--tp18426787p18426787.html
Sent from the Maven - SCM mailing list archive at Nabble.com.
Re: Release/SCM broken for eclipse?
Posted by ChrisGWarp <Ch...@aami.com.au>.
Dennis Lundberg-2 wrote:
>
> ChrisGWarp wrote:
>>
>>
>> Dennis Lundberg-2 wrote:
>>> How have you configured <scm> in your projects?
>>>
>>>
>>>
>>
>> Yes, in all of them. I've even tried only on the base/project Pom. Each
>> project/module has the scm pointing directly to their individual
>> directories.
>>
>> The only thing of note is that I'm using the
>> http://userid:password@server/path form in the scm - not that that should
>> make any difference (but you never know!)
>
> I remember having trouble with that syntax for a project that used CVS,
> but that was a while back. Unfortunately that environment is no longer
> present. Just to be sure, you could try removing the user/password part
> from your SCM URL and specifying them on the command line or in your
> settings.xml instead. That is the preferred way to do it.
>
>
After I ran into issues with the multi module project, I went back and did a
release:prepare/perform on a another single project (one with no relative
paths etc) that produces a single jar file.
There were no issues there, so I took it that they way in which I had all of
the userid/passwords in the SCM URL's was ok.
I do have one further question though.
Should each module of a multi module project have it's own SCM entries,
pointing directly to where they live, or should it just be specified in the
multi module pom only? Also, should we have a trailing slash or not?
I'll see if I can work out how to do the settings.xml bit for the
userid/passwords, as that is a much nicer way of doing things.
Thanks for your help!
-Chris
--
View this message in context: http://www.nabble.com/Release-SCM-broken-for-eclipse--tp18426787p18455361.html
Sent from the Maven - SCM mailing list archive at Nabble.com.
Re: Release/SCM broken for eclipse?
Posted by ChrisGWarp <Ch...@aami.com.au>.
Ok, I've created a public svn repo that you can get to:
http://svn.warpspeed.com.au/test-repos/
everything that you need is in there.
The problem still occurs:
[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)
So, I'm stumped...
Hope you guys can help.
-Chris
--
View this message in context: http://www.nabble.com/Release-SCM-broken-for-eclipse--tp18426787p18478846.html
Sent from the Maven - SCM mailing list archive at Nabble.com.
Re: Release/SCM broken for eclipse?
Posted by Dennis Lundberg <de...@apache.org>.
ChrisGWarp wrote:
>
>
> Dennis Lundberg-2 wrote:
>> How have you configured <scm> in your projects?
>>
>>
>>
>
> Yes, in all of them. I've even tried only on the base/project Pom. Each
> project/module has the scm pointing directly to their individual
> directories.
>
> The only thing of note is that I'm using the
> http://userid:password@server/path form in the scm - not that that should
> make any difference (but you never know!)
I remember having trouble with that syntax for a project that used CVS,
but that was a while back. Unfortunately that environment is no longer
present. Just to be sure, you could try removing the user/password part
from your SCM URL and specifying them on the command line or in your
settings.xml instead. That is the preferred way to do it.
>
> -Chris
>
--
Dennis Lundberg
Re: Release/SCM broken for eclipse?
Posted by ChrisGWarp <Ch...@aami.com.au>.
Dennis Lundberg-2 wrote:
>
> How have you configured <scm> in your projects?
>
>
>
Yes, in all of them. I've even tried only on the base/project Pom. Each
project/module has the scm pointing directly to their individual
directories.
The only thing of note is that I'm using the
http://userid:password@server/path form in the scm - not that that should
make any difference (but you never know!)
-Chris
--
View this message in context: http://www.nabble.com/Release-SCM-broken-for-eclipse--tp18426787p18435342.html
Sent from the Maven - SCM mailing list archive at Nabble.com.
Re: Release/SCM broken for eclipse?
Posted by Dennis Lundberg <de...@apache.org>.
How have you configured <scm> in your projects?
ChrisGWarp wrote:
> Hi all.
>
> From what I can gather, the release plugin has been fixed to work with
> the flattened eclipse based project structure.
>
> But the results that I'm getting below tend to make me think that it is
> the SCM plugin causing me the grief, and I cann't image that I'm doing
> anything that out of the ordinary, so perhaps someone can point out what
> I've done wrong.
>
> I have 4 directories, all at the same level so that they work with
> eclipse.
>
> <workspace dir>\FireDragon (the J2EE Multi Module Build Project)
> <workspace dir>\FireDragonResources (the resources project)
> <workspace dir>\FireDragonWeb (the web/war project)
> <workspace dir>\FireDragonEAR (the ear project).
>
> The multi module build project has this in it:
>
> <modules>
> <module>../FireDragonResources</module>
> <module>../FireDragonWeb</module>
> <module>../FireDragonEAR</module>
> </modules>
>
> And each of the modules (Resources, WAR, EAR) have this as the parent:
>
> <parent>
> <groupId>au.com.warpspeed.firedragon</groupId>
> <artifactId>FireDragon</artifactId>
> <version>1.0.5-SNAPSHOT</version>
> <relativePath>../FireDragon/pom.xml</relativePath>
> </parent>
>
> The project builds fine, so all of that is ok.
>
> However, when I do a release:prepare, I get this as the final bit of the
> output:
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> ------------------------------------------------------------------------
> [INFO] FireDragon - J2EE Multi Module Project ................
> SUCCESS [13.125s]
> [INFO] FireDragon - Resources Project ........................
> SUCCESS [3.875s]
> [INFO] FireDragon - WAR Project ..............................
> SUCCESS [3:36.109s]
> [INFO] FireDragon - EAR Project ..............................
> SUCCESS [1:10.562s]
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 5 minutes 7 seconds
> [INFO] Finished at: Sat Jul 12 21:38:26 EST 2008
> [INFO] Final Memory: 19M/41M
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Checking in modified POMs...
> [INFO] Executing: svn --username chris --password ***** --non-interactive
> commit --file C:\DOCUME~1\Chris\LOCALS~1\Temp\maven-scm-108910589.commi
> t --targets C:\DOCUME~1\Chris\LOCALS~1\Temp\maven-scm-3540-targets
> [INFO] Working directory: C:\Documents and Settings\Chris\My
> Documents\IBM\rationalsdp7.0\workspace\FireDragon
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Unable to commit files
> Provider message:
> The svn command failed.
> Command output:
> svn: 'C:\Documents and Settings\Chris\My
> Documents\IBM\rationalsdp7.0\workspace' is not a working copy
> svn: Can't open file 'C:\Documents and Settings\Chris\My
> Documents\IBM\rationalsdp7.0\workspace\.svn\entries': The system cannot find
> the path specified.
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 5 minutes 24 seconds
> [INFO] Finished at: Sat Jul 12 21:38:28 EST 2008
> [INFO] Final Memory: 7M/13M
> [INFO]
> ------------------------------------------------------------------------
>
> Is the release plugin not really fixed (as claimed since beta-6 and I'm
> using beta-8) or have I done something else that is wrong?
>
> -Chris
>
--
Dennis Lundberg
Re: Release/SCM broken for eclipse?
Posted by ChrisGWarp <Ch...@aami.com.au>.
Jason van Zyl-2 wrote:
>
> It doesn't look to me like there is a project structure that validates
> that in the release project so I can't tell you for sure whether it
> works or not.
>
> If you want to make a sample project for testing we would be happy to
> try and get it to work.
>
I'll try to put one together today.
Thanks.
-Chris
--
View this message in context: http://www.nabble.com/Release-SCM-broken-for-eclipse--tp18426787p18435291.html
Sent from the Maven - SCM mailing list archive at Nabble.com.
Re: Release/SCM broken for eclipse?
Posted by Jason van Zyl <ja...@maven.org>.
It doesn't look to me like there is a project structure that validates
that in the release project so I can't tell you for sure whether it
works or not.
If you want to make a sample project for testing we would be happy to
try and get it to work.
On 13-Jul-08, at 3:06 AM, ChrisGWarp wrote:
>
> Hi all.
>
> From what I can gather, the release plugin has been fixed to work
> with
> the flattened eclipse based project structure.
>
> But the results that I'm getting below tend to make me think that
> it is
> the SCM plugin causing me the grief, and I cann't image that I'm doing
> anything that out of the ordinary, so perhaps someone can point out
> what
> I've done wrong.
>
> I have 4 directories, all at the same level so that they work with
> eclipse.
>
> <workspace dir>\FireDragon (the J2EE Multi Module Build Project)
> <workspace dir>\FireDragonResources (the resources project)
> <workspace dir>\FireDragonWeb (the web/war project)
> <workspace dir>\FireDragonEAR (the ear project).
>
> The multi module build project has this in it:
>
> <modules>
> <module>../FireDragonResources</module>
> <module>../FireDragonWeb</module>
> <module>../FireDragonEAR</module>
> </modules>
>
> And each of the modules (Resources, WAR, EAR) have this as the
> parent:
>
> <parent>
> <groupId>au.com.warpspeed.firedragon</groupId>
> <artifactId>FireDragon</artifactId>
> <version>1.0.5-SNAPSHOT</version>
> <relativePath>../FireDragon/pom.xml</relativePath>
> </parent>
>
> The project builds fine, so all of that is ok.
>
> However, when I do a release:prepare, I get this as the final bit
> of the
> output:
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> ------------------------------------------------------------------------
> [INFO] FireDragon - J2EE Multi Module Project ................
> SUCCESS [13.125s]
> [INFO] FireDragon - Resources Project ........................
> SUCCESS [3.875s]
> [INFO] FireDragon - WAR Project ..............................
> SUCCESS [3:36.109s]
> [INFO] FireDragon - EAR Project ..............................
> SUCCESS [1:10.562s]
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 5 minutes 7 seconds
> [INFO] Finished at: Sat Jul 12 21:38:26 EST 2008
> [INFO] Final Memory: 19M/41M
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Checking in modified POMs...
> [INFO] Executing: svn --username chris --password ***** --non-
> interactive
> commit --file C:\DOCUME~1\Chris\LOCALS~1\Temp\maven-
> scm-108910589.commi
> t --targets C:\DOCUME~1\Chris\LOCALS~1\Temp\maven-scm-3540-targets
> [INFO] Working directory: C:\Documents and Settings\Chris\My
> Documents\IBM\rationalsdp7.0\workspace\FireDragon
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Unable to commit files
> Provider message:
> The svn command failed.
> Command output:
> svn: 'C:\Documents and Settings\Chris\My
> Documents\IBM\rationalsdp7.0\workspace' is not a working copy
> svn: Can't open file 'C:\Documents and Settings\Chris\My
> Documents\IBM\rationalsdp7.0\workspace\.svn\entries': The system
> cannot find
> the path specified.
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 5 minutes 24 seconds
> [INFO] Finished at: Sat Jul 12 21:38:28 EST 2008
> [INFO] Final Memory: 7M/13M
> [INFO]
> ------------------------------------------------------------------------
>
> Is the release plugin not really fixed (as claimed since beta-6
> and I'm
> using beta-8) or have I done something else that is wrong?
>
> -Chris
>
> --
> View this message in context: http://www.nabble.com/Release-SCM-broken-for-eclipse--tp18426787p18426787.html
> Sent from the Maven - SCM mailing list archive at Nabble.com.
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
First, the taking in of scattered particulars under one Idea,
so that everyone understands what is being talked about ... Second,
the separation of the Idea into parts, by dividing it at the joints,
as nature directs, not breaking any limb in half as a bad carver might.
-- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
Re: Release/SCM broken for eclipse?
Posted by ChrisGWarp <Ch...@aami.com.au>.
Dennis Lundberg-2 wrote:
>
> ChrisGWarp wrote:
>> Hi all.
>>
>> From what I can gather, the release plugin has been fixed to work
>> with
>> the flattened eclipse based project structure.
>>
>> But the results that I'm getting below tend to make me think that it
>> is
>> the SCM plugin causing me the grief, and I cann't image that I'm doing
>> anything that out of the ordinary, so perhaps someone can point out what
>> I've done wrong.
>>
>> I have 4 directories, all at the same level so that they work with
>> eclipse.
>>
>> <workspace dir>\FireDragon (the J2EE Multi Module Build Project)
>> <workspace dir>\FireDragonResources (the resources project)
>> <workspace dir>\FireDragonWeb (the web/war project)
>> <workspace dir>\FireDragonEAR (the ear project).
>>
>> The multi module build project has this in it:
>>
>> <modules>
>> <module>../FireDragonResources</module>
>> <module>../FireDragonWeb</module>
>> <module>../FireDragonEAR</module>
>> </modules>
>>
>> And each of the modules (Resources, WAR, EAR) have this as the
>> parent:
>>
>> <parent>
>> <groupId>au.com.warpspeed.firedragon</groupId>
>> <artifactId>FireDragon</artifactId>
>> <version>1.0.5-SNAPSHOT</version>
>> <relativePath>../FireDragon/pom.xml</relativePath>
>> </parent>
>>
>> The project builds fine, so all of that is ok.
>>
>> However, when I do a release:prepare, I get this as the final bit of
>> the
>> output:
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Reactor Summary:
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] FireDragon - J2EE Multi Module Project ................
>> SUCCESS [13.125s]
>> [INFO] FireDragon - Resources Project ........................
>> SUCCESS [3.875s]
>> [INFO] FireDragon - WAR Project ..............................
>> SUCCESS [3:36.109s]
>> [INFO] FireDragon - EAR Project ..............................
>> SUCCESS [1:10.562s]
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD SUCCESSFUL
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 5 minutes 7 seconds
>> [INFO] Finished at: Sat Jul 12 21:38:26 EST 2008
>> [INFO] Final Memory: 19M/41M
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Checking in modified POMs...
>> [INFO] Executing: svn --username chris --password ***** --non-interactive
>> commit --file C:\DOCUME~1\Chris\LOCALS~1\Temp\maven-scm-108910589.commi
>> t --targets C:\DOCUME~1\Chris\LOCALS~1\Temp\maven-scm-3540-targets
>> [INFO] Working directory: C:\Documents and Settings\Chris\My
>> Documents\IBM\rationalsdp7.0\workspace\FireDragon
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Unable to commit files
>> Provider message:
>> The svn command failed.
>> Command output:
>> svn: 'C:\Documents and Settings\Chris\My
>> Documents\IBM\rationalsdp7.0\workspace' is not a working copy
>> svn: Can't open file 'C:\Documents and Settings\Chris\My
>> Documents\IBM\rationalsdp7.0\workspace\.svn\entries': The system cannot
>> find
>> the path specified.
>
> Hang on a second, Subversion is telling us that your directory
> "workspace" is not under version control here. And that is a correct
> observation, since your parent is in the "FireDragon" directory.
>
> I wonder who is telling svn to perform svn operations on that directory.
> Would you mind sharing the --file and --target temporary files with us,
> as they might give us some clues.
>
>
Yes, that is precisely the problem I've got. It is going one level to high
into the the eclipse workspace directory (which is called workspace - just
to add to to the confusion).
I'm happy to share anything with you, but I don't understand exactly what
you're asking for (--file ???).
I'm in the process of setting up a copy of this project (it is a 300Mb
WAR/EAR file, so I'll trim it down a bit... :-)) on a publically access
subversion repo on the same machine. I'll remove the passwords and let you
know when it's done. That way you can have a working reference to play with.
-Chris
--
View this message in context: http://www.nabble.com/Release-SCM-broken-for-eclipse--tp18426787p18455294.html
Sent from the Maven - SCM mailing list archive at Nabble.com.
Re: Release/SCM broken for eclipse?
Posted by ChrisGWarp <Ch...@aami.com.au>.
Dennis Lundberg-2 wrote:
>
>> [INFO] Checking in modified POMs...
>> [INFO] Executing: svn --username chris --password ***** --non-interactive
>> commit --file C:\DOCUME~1\Chris\LOCALS~1\Temp\maven-scm-108910589.commi
>> t --targets C:\DOCUME~1\Chris\LOCALS~1\Temp\maven-scm-3540-targets
>> [INFO] Working directory: C:\Documents and Settings\Chris\My
>> Documents\IBM\rationalsdp7.0\workspace\FireDragon
>
> Hang on a second, Subversion is telling us that your directory
> "workspace" is not under version control here. And that is a correct
> observation, since your parent is in the "FireDragon" directory.
>
> I wonder who is telling svn to perform svn operations on that directory.
> Would you mind sharing the --file and --target temporary files with us,
> as they might give us some clues.
>
Doh. (Pre coffee time for me, sorry). Now I see what you're after.
I went looking for them myself and they'd been deleted, so I'll see if I can
pause the build before it deletes them and send them on to you.
Thanks Again.
-Chris
--
View this message in context: http://www.nabble.com/Release-SCM-broken-for-eclipse--tp18426787p18455401.html
Sent from the Maven - SCM mailing list archive at Nabble.com.
Re: Release/SCM broken for eclipse?
Posted by ChrisGWarp <Ch...@aami.com.au>.
Dennis Lundberg-2 wrote:
>
> Hang on a second, Subversion is telling us that your directory
> "workspace" is not under version control here. And that is a correct
> observation, since your parent is in the "FireDragon" directory.
>
> I wonder who is telling svn to perform svn operations on that directory.
> Would you mind sharing the --file and --target temporary files with us,
> as they might give us some clues.
>
Unfortunately that is the expected command line behavior in this scenario.
This is an issue with the subversion command line client. It requires a
common anchor point so that it can commit all four (more than two really)
projects as a single atomic commit.
This issue is covered in subversion via:
http://subversion.tigris.org/issues/show_bug.cgi?id=2381
For the scenario above, Subclipse does each individual project as a single
commit (so we loose the atomic commit).
>From comments from the link above, Maven needs to cater for this situation
in a similar way (ie individual commits).
This has been logged as:
http://jira.codehaus.org/browse/SCM-392
It really needs to be fixed ASAP, as it is a critical issue for us.
-Chris
--
View this message in context: http://www.nabble.com/Release-SCM-broken-for-eclipse--tp18426787p19135955.html
Sent from the Maven - SCM mailing list archive at Nabble.com.
Re: Release/SCM broken for eclipse?
Posted by ChrisGWarp <Ch...@aami.com.au>.
Dennis Lundberg-2 wrote:
>
> Hang on a second, Subversion is telling us that your directory
> "workspace" is not under version control here. And that is a correct
> observation, since your parent is in the "FireDragon" directory.
>
> I wonder who is telling svn to perform svn operations on that directory.
> Would you mind sharing the --file and --target temporary files with us,
> as they might give us some clues.
>
Hi Dennis,
Is there anything else that you need? Everything that you need is
publically available for test.
-Chris
--
View this message in context: http://www.nabble.com/Release-SCM-broken-for-eclipse--tp18426787p18525041.html
Sent from the Maven - SCM mailing list archive at Nabble.com.
Re: Release/SCM broken for eclipse?
Posted by Dennis Lundberg <de...@apache.org>.
ChrisGWarp wrote:
> Hi all.
>
> From what I can gather, the release plugin has been fixed to work with
> the flattened eclipse based project structure.
>
> But the results that I'm getting below tend to make me think that it is
> the SCM plugin causing me the grief, and I cann't image that I'm doing
> anything that out of the ordinary, so perhaps someone can point out what
> I've done wrong.
>
> I have 4 directories, all at the same level so that they work with
> eclipse.
>
> <workspace dir>\FireDragon (the J2EE Multi Module Build Project)
> <workspace dir>\FireDragonResources (the resources project)
> <workspace dir>\FireDragonWeb (the web/war project)
> <workspace dir>\FireDragonEAR (the ear project).
>
> The multi module build project has this in it:
>
> <modules>
> <module>../FireDragonResources</module>
> <module>../FireDragonWeb</module>
> <module>../FireDragonEAR</module>
> </modules>
>
> And each of the modules (Resources, WAR, EAR) have this as the parent:
>
> <parent>
> <groupId>au.com.warpspeed.firedragon</groupId>
> <artifactId>FireDragon</artifactId>
> <version>1.0.5-SNAPSHOT</version>
> <relativePath>../FireDragon/pom.xml</relativePath>
> </parent>
>
> The project builds fine, so all of that is ok.
>
> However, when I do a release:prepare, I get this as the final bit of the
> output:
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> ------------------------------------------------------------------------
> [INFO] FireDragon - J2EE Multi Module Project ................
> SUCCESS [13.125s]
> [INFO] FireDragon - Resources Project ........................
> SUCCESS [3.875s]
> [INFO] FireDragon - WAR Project ..............................
> SUCCESS [3:36.109s]
> [INFO] FireDragon - EAR Project ..............................
> SUCCESS [1:10.562s]
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 5 minutes 7 seconds
> [INFO] Finished at: Sat Jul 12 21:38:26 EST 2008
> [INFO] Final Memory: 19M/41M
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Checking in modified POMs...
> [INFO] Executing: svn --username chris --password ***** --non-interactive
> commit --file C:\DOCUME~1\Chris\LOCALS~1\Temp\maven-scm-108910589.commi
> t --targets C:\DOCUME~1\Chris\LOCALS~1\Temp\maven-scm-3540-targets
> [INFO] Working directory: C:\Documents and Settings\Chris\My
> Documents\IBM\rationalsdp7.0\workspace\FireDragon
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Unable to commit files
> Provider message:
> The svn command failed.
> Command output:
> svn: 'C:\Documents and Settings\Chris\My
> Documents\IBM\rationalsdp7.0\workspace' is not a working copy
> svn: Can't open file 'C:\Documents and Settings\Chris\My
> Documents\IBM\rationalsdp7.0\workspace\.svn\entries': The system cannot find
> the path specified.
Hang on a second, Subversion is telling us that your directory
"workspace" is not under version control here. And that is a correct
observation, since your parent is in the "FireDragon" directory.
I wonder who is telling svn to perform svn operations on that directory.
Would you mind sharing the --file and --target temporary files with us,
as they might give us some clues.
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 5 minutes 24 seconds
> [INFO] Finished at: Sat Jul 12 21:38:28 EST 2008
> [INFO] Final Memory: 7M/13M
> [INFO]
> ------------------------------------------------------------------------
>
> Is the release plugin not really fixed (as claimed since beta-6 and I'm
> using beta-8) or have I done something else that is wrong?
>
> -Chris
>
--
Dennis Lundberg