email@example.com wrote on 04/23/2006 11:03:25 AM:
> What happens is that sometimes, when I go to commit, it takes
> Eclipse/Subclipse two revisions on the server to complete the command,
> think) it should only take one. If I create a new package and class,
> both unversioned. I then manually add (through Subclipse) the package
> class to version control, and then proceed with a commit. It takes two
> commits (one for the package directory, and another for the class file
> itself). Both commits have the same commit message.
> Steps to reproduce:
> 0. Create a new Eclipse project, and synchronize it with an active SVN
> repository somewhere.
> 1. Create a new package and class. Adding any code to the class is
> 2. Right click either the file or the package, and add it to version
> through the Team menu.
> 3. Right click on the class file, and commit. This step generates two
> commits, one for the package, and one for the class. The Commit dialog
> this step only shows the .java file in the resources-to-commit view,
> though the directory needs to be committed as well. Bringing up the
> dialog by right clicking on the package (instead of the class file)
> the intended one commit. The intended behavior can also be achieved by
> committing with TortoiseSVN instead of through Subclipse.
As you point out, if you just select the folder, or even some higher
parent folder, you will get it all in one commit. It is certainly not the
ideal behavior, but my guess is that it has always been the way Subclipse
works. I do not think that this is some new behavior in recent versions.
I wouldn't really call it a bug, but if you want to submit a patch that
makes it work better, I'd certainly try to get it committed.
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun Apr 23 18:48:38 2006