[Subclipse-users] package rename bugs
From: Peter Mb <mb.peter_at_yahoo.com>
Date: Fri, 4 Jan 2008 07:55:15 -0800 (PST)
Hello all,
In our company we are developing a Java application using the Eclipse
We are experiencing some package rename peculiarities. Some of which I
First, sometimes, when renaming packages having a common parent
Start out with packages
org.cmopany.core.dao
Each holding a single java file.
Correct the typo by renaming each package, commit and you end up with
org.cmopany.core
both locally and in the repository.
(See the attached 'empty-old-package.log' for a console trail)
The org.cmopany.core package is empty. The java files are (correctly)
We also witnessed situations in which the java file where not properly
Second, renaming a middle package component, after having succesfully
Start out with a package
one.tw.thre
holding a single java file.
rename to
one.tw.three
commit.
All is fine at this point.
Now, rename to
one.two.three
and the commit fails with
Item is out-of-date
A full log trail is attached (middle-rename.log).
Is anyone able to shed some light on this?
Here is some detailed version info:
Eclipse 3.3.0, Build id: I20070625-1500
JDK: SUN jdk1.5.0_08
Regards,
____________________________________________________________________________________
---------------------------------------------------------------------
|
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.