[m2e-users] Eclipse JEE Photon - java.lang.NullPointerException caused b

[anvar cassam-chenaï <ecassamc@xxxxxxxxxxx>]

Good Morning!
I have an issue but I don't know if I should report it to the m2e, JDT 
or the WTP mailing list. So I try the first one.

The following error is generated during the startup of Eclipse Photon JEE.

!ENTRY org.eclipse.core.jobs 4 2 2018-11-08 21:26:39.724
!MESSAGE An internal error occurred during: "Initializing Java Tooling".
!STACK 0
java.lang.NullPointerException
     at 
org.eclipse.m2e.jdt.internal.MavenClasspathContainerInitializer.getBuildPathManager(MavenClasspathContainerInitializer.java:80)
     at 
org.eclipse.m2e.jdt.internal.MavenClasspathContainerInitializer.initialize(MavenClasspathContainerInitializer.java:46)
     at 
org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:3211)
     at 
org.eclipse.jdt.internal.core.JavaModelManager$10.run(JavaModelManager.java:3095)
     at 
org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2292)
     at 
org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2319)
     at 
org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:3157)
     at 
org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:2128)
     at 
org.eclipse.jdt.core.JavaCore.initializeAfterLoad(JavaCore.java:4384)
     at 
org.eclipse.jdt.internal.ui.InitializeAfterLoadJob$RealJob.run(InitializeAfterLoadJob.java:39)
     at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

It causes a popup to be displayed indicating: An internal error occurred 
during: "Initializing Java Tooling".
java.lang.NullPointerException

This is shown in the first screenshot sent in the zip file.

This error is reproducible.

1) Import the two JSF projects

2) Create a Tomcat 8.5 server in the "Servers" Tab and deploy one of the 
JSF projects with the "Add and Remove.." contextual menu.
This is shown in the second screenshot.

3) Restart Eclipse -> The error should occur.

5) I have the same problem with the Glassfish server or the Payara one

6) This error does not happen if no server has been configured in the 
"Servers " tab.

7) If I look in the .log file, i see that another error happens just before
!ENTRY org.eclipse.osgi 2 0 2018-11-08 21:26:20.255
!MESSAGE While loading class 
"org.eclipse.m2e.jdt.internal.MavenClasspathHelpers", thread 
"Thread[Worker-6: Update dynamic Java sources working sets,5,main]" 
timed out waiting (5212ms) for thread "Thread[Worker-3: Decoration 
Calculation,5,main]" to finish starting bundle 
"org.eclipse.m2e.jdt_1.9.1.20180912-1601 [589]". To avoid deadlock, 
thread "Thread[Worker-6: Update dynamic Java sources working 
sets,5,main]" is proceeding but 
"org.eclipse.m2e.jdt.internal.MavenClasspathHelpers" may not be fully 
initialized.
!STACK 0
org.osgi.framework.BundleException: Unable to acquire the state change 
lock for the module: osgi.identity; type="osgi.bundle"; 
version:Version="1.9.1.20180912-1601"; 
osgi.identity="org.eclipse.m2e.jdt"; singleton:="true" [id=589] STARTED 
[STARTED]
     at org.eclipse.osgi.container.Module.lockStateChange(Module.java:340)
  ...

But this one does not generate any error popup.

Do you know if there is a workaround to prevent the first error to 
generate the popup ?

Thank you in advance for any answer.
Anvar C.C.

Attachment: jdt-m2e-issue.zip
Description: jdt-m2e-issue.zip