Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 535472 - Oxygen 3a IllegalArgumentException in ASTParser.<init>
Summary: Oxygen 3a IllegalArgumentException in ASTParser.<init>
Status: RESOLVED NOT_ECLIPSE
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.7.3   Edit
Hardware: PC Windows 10
: P3 blocker with 1 vote (vote)
Target Milestone: 4.8   Edit
Assignee: Stephan Herrmann CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-01 16:44 EDT by Nathan Niesen CLA
Modified: 2018-06-04 10:33 EDT (History)
1 user (show)

See Also:


Attachments
configuration (1.23 MB, text/plain)
2018-06-01 16:59 EDT, Nathan Niesen CLA
no flags Details
error log (65.67 KB, application/octet-stream)
2018-06-01 16:59 EDT, Nathan Niesen CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nathan Niesen CLA 2018-06-01 16:44:03 EDT
This is NOT a duplicate of the three year old bugs (Bug 464655, Bug 464353, Bug 465753) from Recomenders 2.x.

This bug comes from installing feature name: 'Eclipse Java Development Tools'  version: 3.13.4.v20180330-0919 Id: org.eclipse.jdt.feature.group in Oxygen 3 or installing Oxygen 3a. 

I believe it stems from the changes made for Oxygen 3a to support Java 10.

Once the feature is installed, attempting to edit Java and Groovy files generates an AST Parser error for every cursor movement in the source file:

> 'Requesting Java AST from selection' has encountered a problem.

> An internal error occurred during: "Requesting Java AST from selection".
> java.lang.IllegalArgumentException


These are some of the automated report pages with the stack traces and such:
* https://dev.eclipse.org/recommenders/community/aeri/v2/#!/submissions/yVce3nlkEwk8OdclscgbdpfMm5AxAT4TCOD4bFpPew2WFbNEoRAhLSZfldeq8XWC
* https://dev.eclipse.org/recommenders/community/aeri/v2/#!/submissions/IaboUSWu9CwAMVuQlZO8ttksaOn89x7wf1rndcJfK1mrXaUrRBkdmZ0d93mFIR27
* https://dev.eclipse.org/recommenders/community/aeri/v2/#!/problems/5b11a662e4b01659284b2019
* https://dev.eclipse.org/recommenders/community/aeri/v2/#!/submissions/Pj1s86FdIBZqJi2QrXgmXJrl0KYxDU3nsIzYqCZ1MdzNXJiAAXIdTgiSKIycPF2s
* https://dev.eclipse.org/recommenders/community/aeri/v2/#!/problems/5b11ab8fe4b01659284b2049


I've tried numerous times to create new error reports using the automated reporting system but it keeps saying the bug is a duplicate. Clicking the 'Create a new problem report...' for 'Does your error not belong to any of the above problems?' and 'Does your error not belong to this problem?' flashes a message box so fast I can't see what it created or where to find it. Then I usually get a 'Server connection lost, trying to reconnect...' spinner when attempt to add to the report. Likely due to JavaScript errors "Refused to apply style from 'https://dev.eclipse.org/recommenders/community/aeri/APP/PUBLISHED/styles.css' because its MIME type ('application/json') is not a supported stylesheet MIME type, and strict MIME checking is enabled."
Comment 1 Nathan Niesen CLA 2018-06-01 16:59:07 EDT
Created attachment 274311 [details]
configuration
Comment 2 Nathan Niesen CLA 2018-06-01 16:59:52 EDT
Created attachment 274312 [details]
error log
Comment 3 Nathan Niesen CLA 2018-06-01 17:00:55 EDT
Reverting 'Eclipse Java Development Tools'  version: 3.13.4.v20180330-0919 to the previous version fixes the issue but then it nags me about the update.
Comment 4 Nathan Niesen CLA 2018-06-01 17:06:42 EDT
Here's one of my original 'submissions' that didn't seem to go anywhere:
https://dev.eclipse.org/recommenders/community/aeri/v2/#!/submissions/yVce3nlkEwk8OdclscgbdpfMm5AxAT4TCOD4bFpPew2WFbNEoRAhLSZfldeq8XWC
Comment 5 Nathan Niesen CLA 2018-06-01 17:08:37 EDT
(In reply to Nathan Niesen from comment #4)
> Here's one of my original 'submissions' that didn't seem to go anywhere:
> https://dev.eclipse.org/recommenders/community/aeri/v2/#!/submissions/
> yVce3nlkEwk8OdclscgbdpfMm5AxAT4TCOD4bFpPew2WFbNEoRAhLSZfldeq8XWC

This one has steps to reproduce as well as before/after configuraitons, logs, and a screen shot.
Comment 6 Stephan Herrmann CLA 2018-06-02 07:48:34 EDT
From your mentioning of Groovy and from the linke aeri report we learn that you are not using an original version of org.eclipse.jdt.core, see:

org.eclipse.jdt.core   3.13.100.xx-201801041714-e47-RELEASE
org.eclipse.jdt        3.13.4.v20180330-0640
org.eclipse.jdt.ui     3.13.100.v20180330-0726

Similarly in attachment 274311 [details] :

org.eclipse.jdt (3.13.4.v20180330-0640) "Eclipse Java Development Tools" [Resolved]
org.eclipse.jdt.core (3.13.100.xx-201801041714-e47-RELEASE) "Java Development Tools Core" [Active]
org.eclipse.jdt.groovy.core (2.9.2.xx-201801041714-e47-RELEASE) "Groovy-Eclipse Integration" [Active]
org.eclipse.jdt.ui (3.13.100.v20180330-0726) "Java Development Tools UI" [Active]

This looks inconsistent to me. See that jdt.core is older than jdt.ui which should never happen. Please contact the maintainers of groovy eclipse about a release that matches the version of JDT you want to install. Marking as NOT_ECLIPSE because groovy eclipse is not maintained at eclipse.org.

Please re-open, if you can reproduce without groovy eclipse installed.
Comment 7 Nathan Niesen CLA 2018-06-04 10:33:15 EDT
Thank you! 

Here is the Groovy-Eclipse bug report for anyone coming down this path:
https://github.com/groovy/groovy-eclipse/issues/556