| Summary: | IAE in ASTNode.setSourceRange below SharedASTProvider.getAST | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Andreas Sewe <sewe> |
| Component: | Core | Assignee: | Manoj N Palat <manoj.palat> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jarthana, stephan.herrmann |
| Version: | 4.5.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | stalebug | ||
|
Description
Andreas Sewe
(In reply to Andreas Sewe from comment #0) > I unfortunately cannot give you much more information than that, besides the > following version info: > > - org.eclipse.jdt.core 3.11.2.xx-201708152349-e45 > - org.eclipse.jdt.ui 3.11.2.v20151123-1510 > > - org.eclipse.epp.package.java.product 4.5.2.M20160212-1500 Looks like s.o. installed a recent STS over an older original Eclipse package. o.e.jdt.core is not in a version that is produced by JDT, nor does this version seem to be compatible with the installed version of o.e.jdt.ui. > The version is, of course, pre-Neon, so this issue might have indeed be fixed > with Bug 460186, but as I said, the stacktraces are quite different. Different line numbers _could_ be an effect of the modifications done by the Spring team (assumably: groovy-eclipse). Ideally, the reporter should tell whether the problem can be reproduced with original and consistent versions of jdt plug-ins. 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. |