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

Re: [Subclipse-users] Refactoring bug with Eclipse 3.2

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-08-02 22:36:03 CEST

Thorsten Meinl <Thorsten.Meinl@uni-konstanz.de> wrote on 08/02/2006
04:28:34 PM:

> Eclipse 3.2 has a nice refactoring feature which allows to rename a
> package and all its sub-packages. This does not work however with
subclipse.
> Suppose you have a package and class hierarchy like this
>
> knime.nodes.io.table.reader.A
> knime.nodes.io.table.writer.B
>
> and you want to rename package knime.nodes to knime.node including all
> its subpackages. If you do this you will get an subclipse error
> "svn: '/home/thor/workspace/KNIME/Test/src/knime/node' already under
> version control"
>
> Here is a full trace of all subclipse operations:
>
> =======================================================
> add-N /home/thor/workspace/KNIME/Test/src/knime/node
> A /home/thor/workspace/KNIME/Test/src/knime/node
> add-N /home/thor/workspace/KNIME/Test/src/knime/node/io
> A /home/thor/workspace/KNIME/Test/src/knime/node/io
> add-N /home/thor/workspace/KNIME/Test/src/knime/node/io/table
> A /home/thor/workspace/KNIME/Test/src/knime/node/io/table
> move /home/thor/workspace/KNIME/Test/src/knime/nodes/io/table/reader
> /home/thor/workspace/KNIME/Test/src/knime/node/io/table/reader
> A /home/thor/workspace/KNIME/Test/src/knime/node/io/table/reader
> D
> /home/thor/workspace/KNIME/Test/src/knime/nodes/io/table/reader/C.java
> D
> /home/thor/workspace/KNIME/Test/src/knime/nodes/io/table/reader
> add-N /home/thor/workspace/KNIME/Test/src/knime/node
> svn: '/home/thor/workspace/KNIME/Test/src/knime/node' already under
> version control
> =======================================================
>
> I believe this is a bug. Subclipse doesn't seem to recognize that it
> suffices to just move the src/knime/nodes directory and not all
> sub-directories.

Are you using Subclipse 1.1.4? I recently did refactorings like this and
did not have a problem. But someone else did have it recently. I have
not been able to reproduce it. This problem was specifically fixed in one
of the recent releases, which is why I want to know the version.

And the main problem was just that our status cache did not know we had
already added the package so we tried to do it again when we needed to.
The fix was to refresh the cache after adding the package.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Aug 2 22:36:16 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.