Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jdt-dev] Problem while refactoring subpackages since update to Eclipse Europe


Hi Christian

This sounds like https://bugs.eclipse.org/bugs/show_bug.cgi?id=192638 ,
which occured in 3.3 and was fixed for 3.3.1.

Please check your scenario with a recent maintenance build. If you can still reproduce the problem, please file a new bug.

Thanks,
Markus



"Christian Wörns" <christian.woerns@xxxxxxxxxxxxxx>
Sent by: jdt-dev-bounces@xxxxxxxxxxx

2007-08-30 14:25

Please respond to
"Eclipse JDT general developers list." <jdt-dev@xxxxxxxxxxx>

To
jdt-dev@xxxxxxxxxxx
cc
Subject
[jdt-dev] Problem while refactoring subpackages since update to        Eclipse Europe





Hi!

Since I updated Eclipse from Version 3.2 to 3.3 (Europe) I get invalid code after refactoring.

Periodically I have to refactor an automatic generated Java source code because the package and class names are the same like other package names. The automatic generated structure looks like:

com.package
com.package.one
com.package.one.other
com.package.two

To refactor the project I rename the package "com.package" to "com.package.specific". In Eclipse 3.2 and earlier versions all references, also in the sub packages would be updated. Since updating to Eclipse 3.3 the package-names and the sub package-names would be correctly renamed, but the references in the source code would not be corrected - in the main-package they are.

I use: right click on package-name -> Refactor -> Rename...
"Update references" and "Rename subpackages" are checked.

Did I do something wrong? Have I overlooked a hidden configuration?
Is this maybe a known bug because the algorithm got changed?

Best regards,
  Christian Wörns
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jdt-dev


Back to the top