Community
Participate
Working Groups
The following incident was reported via the automated error reporting: The user provided the following details for this incident: Ctrl+click on class constructor GenericXmlApplicationContext (Spring). I suspect that this Gradle module still keeps a reference to an older version of Spring than the rest of the modules (although they all are configured to use the same Spring version 4.1.1.RELEASE). code: 10,001 plugin: org.eclipse.jdt.ui_3.10.100.v20150116-1347 message: HIDDEN fingerprint: f23efde1 exception class: org.eclipse.jdt.core.JavaModelException exception message: HIDDEN number of children: 1 org.eclipse.jdt.core.JavaModelException: HIDDEN at org.eclipse.jdt.internal.core.PackageFragmentRoot.getResolvedClasspathEntry(PackageFragmentRoot.java:578) at org.eclipse.jdt.internal.corext.javadoc.JavaDocLocations.getJavadocBaseLocation(JavaDocLocations.java:310) at org.eclipse.jdt.internal.corext.javadoc.JavaDocLocations.getJavadocLocation(JavaDocLocations.java:450) at org.eclipse.jdt.ui.JavaUI.getJavadocLocation(JavaUI.java:985) at org.eclipse.jdt.internal.corext.javadoc.JavaDocLocations.getBaseURL(JavaDocLocations.java:629) at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.getHoverInfo(JavadocHover.java:697) at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.internalGetHoverInfo(JavadocHover.java:609) at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.getHoverInfo2(JavadocHover.java:601) at org.eclipse.jdt.internal.ui.text.java.hover.BestMatchHover.getHoverInfo2(BestMatchHover.java:163) at org.eclipse.jdt.internal.ui.text.java.hover.BestMatchHover.getHoverInfo2(BestMatchHover.java:129) at org.eclipse.jdt.internal.ui.text.java.hover.JavaEditorTextHoverProxy.getHoverInfo2(JavaEditorTextHoverProxy.java:85) at org.eclipse.jface.text.TextViewerHoverManager$4.run(TextViewerHoverManager.java:166) --- code: 1,006 plugin: org.eclipse.jdt.core_3.11.0.v20150126-2015 message: HIDDEN fingerprint: 00000000 number of children: 0 General Information: reported-by: Knut-Olav Hoven anonymous-id: 61defd3a-be30-4886-b3df-46ef0a4a2664 eclipse-build-id: 4.5.0.I20150203-1300 eclipse-product: org.eclipse.epp.package.dsl.product operating system: Linux 3.16.0 (x86_64) - gtk jre-version: 1.7.0_07-b10 The following plug-ins were present on the execution stack (*): 1. org.eclipse.jdt.core_3.11.0.v20150126-2015 2. org.eclipse.jdt_3.11.0.v20150203-1300 3. org.eclipse.jdt.ui_3.10.100.v20150116-1347 4. org.eclipse.jface.text_3.10.0.v20150112-1146 5. org.eclipse.jface_3.11.0.v20150121-1751 Please note that: * Messages, stacktraces, and nested status objects may be shortened. * Bug fields like status, resolution, and whiteboard are sent back to reporters. * The list of present bundles and their respective versions was calculated by package naming heuristics. This may or may not reflect reality. Other Resources: * Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/54db768ae4b0948555dad751 * Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide Thank you for your assistance. Your friendly error-reports-inbox.
I believe that for investigation we'd minimally need the message from the JavaModelException (report says "HIDDEN"). Additionally I'm surprised to see the original version of org.eclipse.jdt.core, although mentioning of Spring and gradle could suggest that the patched variant from Groovy-Eclipse is being used - just mentioning.
There is new information available. Did you check 'similar incidents'? [1] https://dev.eclipse.org/recommenders/committers/confess/#/problems/54db768ae4b0948555dad751/similar
(In reply to Stephan Herrmann from comment #1) > Additionally I'm surprised to see the original version of > org.eclipse.jdt.core, although mentioning of Spring and gradle could suggest > that the patched variant from Groovy-Eclipse is being used - just mentioning. Generally: Is it worth to check for presence of certain bundles before sending an error report? We do something similar in bug 466848 where we provide further details in case of linkage errors.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
