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

Re: [Subclipse-users] Defects not in list?

From: DM Smith <dmsmith555_at_yahoo.com>
Date: 2006-02-13 15:50:02 CET

Karl Auer wrote:
> On Mon, 2006-02-13 at 08:46 -0500, Mark Phippard wrote:
>>> - Project P is under version control
>>> - rename package "X.Y.Z" in project P to "X.Y.C.D"
>>> - commit the project "P"
>>> - Subversion (via Subclipse) complains that "X.Y.Z" is out of date.
>>> The workaround is to do Team->Update on Project P, then commit, but IMHO
>>> this should not be necessary.
>> This is a Subversion requirement. There is no way that Subclipse is going
>> to fire off an update command without you telling us, so I do not see what
>> else could be done here.
> I'm not understanding something; why is the update necessary at all? I'm
> committing, which to my way of thinking means more or less "this is how
> I want the directory to look; make it so". Maybe I just don't understand
> what exactly "out of date' means.
Have you tried this sequence from the command line.
(I know that it really needs to be done in Eclipse to get the
refactoring done, but I mean as a test.)
I think that it should work the same way.

By the way, if X.Y.Z was out of date before the refactoring, the command
line will produce the results you mention above. Refactoring should only
be done after the user has updated both the source and the target (and I
think their ancestors)

To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Feb 13 15:50:39 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.