Bug 561846 - java.lang.IllegalArgumentException Errors running builder 'API Analysis Builder'
Summary: java.lang.IllegalArgumentException Errors running builder 'API Analysis Builder'
Status: RESOLVED WORKSFORME
Alias: None
Product: PDE
Classification: Eclipse Project
Component: API Tools (show other bugs)
Version: 4.15   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Vikas Chandra CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2020-04-07 02:11 EDT by Karsten Thoms CLA
Modified: 2020-04-27 08:56 EDT (History)
2 users (show)

See Also:


Attachments
Screenshot (84.04 KB, image/png)
2020-04-07 02:11 EDT, Karsten Thoms CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Karsten Thoms CLA 2020-04-07 02:11:40 EDT
Created attachment 282366 [details]
Screenshot

In my platform dev workspace (4.15) I am getting frequently IllegalArgumentExceptions from the API tools builder.

- org.eclipse.jdt.core
 version 3.21.0.v20200304-1404	
- org.eclipse.pde.api.tools 1.1.1300.v20200318-1350	

java.lang.IllegalArgumentException
	at org.eclipse.jdt.core.dom.ASTParser.<init>(ASTParser.java:241)
	at org.eclipse.jdt.core.dom.ASTParser.newParser(ASTParser.java:134)
	at org.eclipse.pde.api.tools.internal.provisional.scanner.TagScanner.scan(TagScanner.java:660)
	at org.eclipse.pde.api.tools.internal.provisional.scanner.TagScanner.scan(TagScanner.java:636)
	at org.eclipse.pde.api.tools.internal.ProjectApiDescription$TypeNode.refresh(ProjectApiDescription.java:250)
	at org.eclipse.pde.api.tools.internal.ApiDescription.findNode(ApiDescription.java:431)
	at org.eclipse.pde.api.tools.internal.ProjectApiDescription.visit(ProjectApiDescription.java:403)
	at org.eclipse.pde.api.tools.internal.ProjectApiDescription.accept(ProjectApiDescription.java:372)
	at org.eclipse.pde.api.tools.internal.builder.ReferenceAnalyzer.buildProblemDetectors(ReferenceAnalyzer.java:304)
	at org.eclipse.pde.api.tools.internal.builder.ReferenceAnalyzer.analyze(ReferenceAnalyzer.java:233)
	at org.eclipse.pde.api.tools.internal.builder.BaseApiAnalyzer.checkApiUsage(BaseApiAnalyzer.java:1249)
	at org.eclipse.pde.api.tools.internal.builder.BaseApiAnalyzer.analyzeComponent(BaseApiAnalyzer.java:285)
	at org.eclipse.pde.api.tools.internal.builder.ApiAnalysisBuilder.buildAll(ApiAnalysisBuilder.java:799)
	at org.eclipse.pde.api.tools.internal.builder.ApiAnalysisBuilder.build(ApiAnalysisBuilder.java:427)
	at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:832)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:220)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:263)
	at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:316)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:319)
	at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:371)
	at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:392)
	at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:154)
	at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:244)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Comment 1 Michael Keppler CLA 2020-04-07 03:56:04 EDT
Do you have a Java 14 project in that workspace (maybe just for playing around)? That parser class only knows up to Java 13 and throws that exception for unknown Java levels in your version of jdt.core.

I think you must upgrade to the milestone releases (or install the Java 14 support from marketplace) to be able to use Java 14, right?
Comment 2 Karsten Thoms CLA 2020-04-07 04:39:42 EDT
The dev IDE is started with an AdoptOpenJDK 8. Additionally configured is an AdoptOpenJDK 11.
Comment 3 Vikas Chandra CLA 2020-04-07 06:51:56 EDT
I looked at this. You have taken latest PDE code but not latest JDT code. 
Or you have taken 4.15 eclipse and master code from PDE.

I think you should either take 4.15 with R4_15_maintenance code or 4.16 with master code.

If you want to work on 4.15 with master code from PDE, additionally take jdt.core's master code too. That would work too.

Let me know if any of the solutions mentioned above works for you.
Comment 4 Michael Keppler CLA 2020-04-13 00:56:38 EDT
Karsten, I have the same issue meanwhile in all workspaces after upgrading to the 4.16 M1 version via Oomph. At least for me the problem is that the top level EPP package prohibits upgrading JDT due to some conflict. You may want to run Help->Upgrade, to see if you have a similar conflict.
Comment 5 Michael Keppler CLA 2020-04-17 08:31:56 EDT
For me the issue has vanished after upgrading to https://download.eclipse.org/staging/2020-06/, since that resolves the conflicting JDT dependency.

Karsten, please verify.
Comment 6 Vikas Chandra CLA 2020-04-27 07:08:57 EDT
Marking works for me based on last comment