Community
Participate
Working Groups
What steps will reproduce the problem? 1. I have Java project B that depends on Java project A 2. Java project A has in its buildpath the provided JAR, which is also exported (i.e.: checked in Java build path | Order and export) 3. in project B I have an interface with a method defined as: int getVersion() 4. if I try to rename that method to anything else, I get the provided exception My suspect is that the provided JAR has that 1.0.org.etc. structure in it that is causing annoyance to JDT. -- Error Details -- Date: Wed Mar 03 15:00:46 CET 2010 Message: Internal Error Severity: Error Product: Eclipse Platform 3.3.202.v201002111343 (org.eclipse.platform.ide) Plugin: org.eclipse.jdt.ui Session Data: eclipse.buildId= java.version=1.6.0_18 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=it_IT Command-line arguments: -os win32 -ws win32 -arch x86_64 Exception Stack Trace: java.lang.reflect.InvocationTargetException at org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:110) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Caused by: Java Model Exception: Java Model Status [1.0.org.apache.xml.resolver [in D:\workspace35\Librerie condivise K5.1.2\jaxb-xjc-2.1.7.jar] does not exist] at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:502) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:246) at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:504) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:240) at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107) at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:515) at org.eclipse.jdt.internal.core.BinaryType.getElementInfo(BinaryType.java:285) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:238) at org.eclipse.jdt.internal.core.BinaryType.isInterface(BinaryType.java:722) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.findAllRippleMethods(RippleMethodFinder2.java:242) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.getAllRippleMethods(RippleMethodFinder2.java:168) at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.getRelatedMethods(RippleMethodFinder2.java:161) at org.eclipse.jdt.internal.corext.refactoring.rename.RenameMethodProcessor.initializeMethodsToRename(RenameMethodProcessor.java:236) at org.eclipse.jdt.internal.corext.refactoring.rename.RenameMethodProcessor.doCheckFinalConditions(RenameMethodProcessor.java:360) at org.eclipse.jdt.internal.corext.refactoring.rename.RenameVirtualMethodProcessor.doCheckFinalConditions(RenameVirtualMethodProcessor.java:143) at org.eclipse.jdt.internal.corext.refactoring.rename.JavaRenameProcessor.checkFinalConditions(JavaRenameProcessor.java:46) at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:224) at org.eclipse.ltk.core.refactoring.Refactoring.checkAllConditions(Refactoring.java:160) at org.eclipse.jdt.internal.ui.refactoring.RefactoringExecutionHelper$Operation.run(RefactoringExecutionHelper.java:80) at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:39) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:728) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:4694) at org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:106) ... 1 more
Bugzilla is preventing me from attaching the JAR here. However, here is a link to download it: ftp://guest:guest@mauromol.dyndns.org/part0/public/jaxb-xjc-2.1.7.jar
Looks like a duplicate of bug 293861. Can you try again with 3.6M5 or a newer I-build ?
It seems to be the same bug, sorry for not finding it out. I tried a search in Bugzilla with the Exception but couldn't find any related issue. I'm going to test 3.6, anyway I think you can already close this now. Thank you!
Well, I can do it by myself :-P *** This bug has been marked as a duplicate of bug 293861 ***