Re: AW: Why using flattened structure [was Re: [VOTE] Release Maven Scm 1.1 (take 3)]

2008-08-26 Thread ChrisGWarp
struberg wrote: And why you don't want to use this structure ?. I guess the main argument is that eclipse cannot nest projects, so there's no way to edit your parent pom (+ parent site, etc) with eclipse (instead you have to vi + svn commit on the command line). BUT: My gut feeling

Re: [VOTE] Release Maven Scm 1.1 (take 3)

2008-08-25 Thread ChrisGWarp
Olivier Lamy wrote: Hi, For me it's not a SCM issue !. Don't use flat structure and it will works like a charm ! Move all files which are in http://svn.warpspeed.com.au/test-repos/FireDragon/trunk/FireDragon/ to http://svn.warpspeed.com.au/test-repos/FireDragon/trunk/ (and change all

Re: [VOTE] Release Maven Scm 1.1 (take 3)

2008-08-25 Thread ChrisGWarp
Olivier Lamy wrote: I will play with your repo in a dedicated branch : http://svn.warpspeed.com.au/test-repos/FireDragon/branches/olamy-test/ Go for it! That is what it is there for. -Chris -- View this message in context:

Re: [VOTE] Release Maven Scm 1.1 (take 3)

2008-08-24 Thread ChrisGWarp
-1 Not until SCM-392 has been fixed. This is a critical issue for us. And I don't imagine that it is that an uncommon a problem either. http://jira.codehaus.org/browse/SCM-392 -Chris -- View this message in context:

Re: Release/SCM broken for eclipse?

2008-08-24 Thread ChrisGWarp
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

Re: Release/SCM broken for eclipse?

2008-07-18 Thread ChrisGWarp
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

Re: Release/SCM broken for eclipse?

2008-07-14 Thread ChrisGWarp
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]

Re: Release/SCM broken for eclipse?

2008-07-13 Thread ChrisGWarp
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

Re: Release/SCM broken for eclipse?

2008-07-13 Thread ChrisGWarp
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