[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] Double commit needed after replacing a file in Eclipse

From: Mark Phippard <markphip_at_gmail.com>
Date: 2006-12-16 00:06:23 CET

On 12/15/06, Jaan Vajakas <jaanvajakas@hot.ee> wrote:
> Here's another issue. Suppose I have two projects - A and B - open in an
> Eclipse workspace, both under version control. I have a file named F in both
> projects (it does not matter whether F is a source code file or some other
> file). Let's say I have a newer version of file F in project A and I want to
> copy it to project B. In Package Explorer I copy file F from project A to
> project B (by dragging it with the mouse while holding down the Control
> key), replacing the file F in project B. Then if I want to commit project B
> I must commit it twice: before the first commit the file F in project B is
> regarded as "deleted", with the first commit the file F is deleted from the
> repository and becomes "unversioned" and with the second commit I can add it
> to the repository again. This double commit is somewhat tedious, thus I
> think something should be changed in Subclipse so that one commit would
> suffice.

This is an issue with Eclipse. We have an issue filed but I do not
expect them to ever address it. We added a Team -> Copy and Team ->
Export option so that you could copy stuff the right way.

In your scenario, two other options would be to cut and paste the
contents of the file between editors and also to do the drag and drop
from Windows Explorer into Eclipse. The problem is only in the drag
and drop within Eclipse,


To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Sat Dec 16 00:06:28 2006

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.