[Subclipse-users] Defects not in list?

Hi there.

As will have been obvious to those seeing my plaintive messages in this
list, the subversion list and the eclipse.platform newsgroup, I have
been doing battle with refactoring.

The first issue is that under some circumstances, even with the build
correct in every detail, Java projects that reference another are NOT
refactored when the project they reference is refactored. The
workaround, which works for reasons completely unfathomable to me, is to
remove the required project from the build path and then put it back!
This seems to me to be an Eclipse bug, so not of concern here.

The second issue is with the way Subclipse handles Java package renames.
This sequence, for example, fails every time for me, with Subversion
complaining that the old package path is out of date:

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

I don't see this in the issues list - am I the only one it happens to?

Also, Mark Phippard said:
> The Checkout and Revert bugs have been fixed and are just
> waiting for the next release.

... but I don't see them in the issues list either; am I looking in the
wrong place, or are they under some unrelated heading?

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer@biplane.com.au)                   +61-2-64957160 (w/h)
http://www.biplane.com.au/~kauer/                  +61-428-957160 (mob)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org