Summary: | [search] Get an internal error while refactoring a method name | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Shone <shone_f> |
Component: | Core | Assignee: | Satyam Kandula <satyam.kandula> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | markus.kell.r, Olivier_Thomann |
Version: | 3.5 | ||
Target Milestone: | 3.6 M4 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Shone
2009-07-28 22:21:58 EDT
We get an IAE in the search engine: java.lang.IllegalArgumentException: Class file name must end with .class at org.eclipse.jdt.internal.core.PackageFragment.getClassFile(PackageFragment.java:182) Moving to Core (may be dup of bug 268933 or bug 269820). Do you have other plugins than Eclipse installed (Galileo ones, others,...)? (In reply to comment #2) > Do you have other plugins than Eclipse installed (Galileo ones, others,...)? > hi, I have SVN installed: org.tigris.subversion.clientadapter.javahl_1.6.3.jar org.tigris.subversion.clientadapter_1.6.0.2.jar org.tigris.subversion.subclipse.core_1.6.2.jar org.tigris.subversion.subclipse.doc_1.3.0.jar org.tigris.subversion.subclipse.ui_1.6.3.jar no other plugins except these. Would it be possible to provide a workspace in which the problem occurs? This looks like a duplicate of bug 268933. So far we were unable to reproduce it. (In reply to comment #4) > Would it be possible to provide a workspace in which the problem occurs? > This looks like a duplicate of bug 268933. So far we were unable to reproduce > it. > Hi All, Sorry, now I can't reproduce this bug either. The error occurred when I ported from 3.4 to 3.5 for the first time. Today I create a new workspace with 3.4 and then load it with 3.5, perform the same refactoring, and it works! Maybe I should have tracked to the line and found out what error it was. I will if I get this error again. Regards Shone Reducing severity. As long as we have no clue how to reproduce the problem, it will be difficult to track it down. Was there any change in the Eclipse version or were there any plugins that would have got modified? Here is one reason that I could see this problem happening: There is a mechanism in place where a plugin can tell Eclipse that a non *.java extension file be considered like a java file. In this case, the Eclipse indexer indexes also these files and keeps the indexes in the workspace. If the same workspace is used when that plugin doesn't exist, then one could end up in this error. Closing as a duplicate of bug 286379. Try 3.6M3 and report if you still get this issue. *** This bug has been marked as a duplicate of bug 286379 *** |