Re: Release/SCM broken for eclipse?

[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.