Skip to main content



      Home
Home » Language IDEs » Java Development Tools (JDT) » Eclipse 2021-06 error on maven pom
Eclipse 2021-06 error on maven pom [message #1842429] Fri, 18 June 2021 11:32 Go to next message
Eclipse UserFriend
I migrated some projects to Eclipse 2021-06 but I get an error :
Unable to make field private final java.util.Comparator java.util.TreeMap.comparator accessible...
on my Maven pom.
Reopening the project with 2021-03 it seems to work.
Is it a bug ?
Tks
Tullio
Re: Eclipse 2021-06 error on maven pom [message #1842446 is a reply to message #1842429] Sat, 19 June 2021 11:18 Go to previous messageGo to next message
Eclipse UserFriend
This isn't a JDT question. It's not clear without a stack trace which component is causing this. Maybe you are using Java 16 and you need the VM option --illegal-access=permit to allow such type of reflection...
Re: Eclipse 2021-06 error on maven pom [message #1842469 is a reply to message #1842446] Mon, 21 June 2021 03:19 Go to previous messageGo to next message
Eclipse UserFriend
I don't see any stack trace (where can I find it, if any ?).
The only visible message is
Unable to make field private final java.util.Comparator java.util.TreeMap.comparator accessible: module java.base does not "opens java.util" to unnamed module @36929d70.
Tks

[Updated on: Mon, 21 June 2021 03:20] by Moderator

Re: Eclipse 2021-06 error on maven pom [message #1842474 is a reply to message #1842469] Mon, 21 June 2021 04:43 Go to previous messageGo to next message
Eclipse UserFriend
You've not explain when/where/how you see this. If this is in the IDE then the Error Log view will likely show the full stack trace (and adding -illegal-access=permit to the eclipse.ini after -vmargs line will perhaps avoid the problem).
Re: Eclipse 2021-06 error on maven pom [message #1842490 is a reply to message #1842474] Mon, 21 June 2021 12:04 Go to previous messageGo to next message
Eclipse UserFriend
Tks for Your help.
The workaround didn't solve the issue.
The error log doesn't show any stack trace but only some warnings.
The resource producing the problems seems to be a pom.xml.
After some formatting of the pom I got a different error :

at org.eclipse.jface.text.TreeLineTracker.getLineInformation(TreeLineTracker.java:1163)
at org.eclipse.jface.text.AbstractLineTracker.getLineInformation(AbstractLineTracker.java:137)
at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.getLineInformation(BasicStructuredDocument.java:1461)
at org.eclipse.lsp4e.LSPEclipseUtils.toOffset(LSPEclipseUtils.java:167)
at org.eclipse.lsp4e.operations.diagnostics.LSPDiagnosticsToMarkers.updateMarker(LSPDiagnosticsToMarkers.java:180)
at org.eclipse.lsp4e.operations.diagnostics.LSPDiagnosticsToMarkers$1.run(LSPDiagnosticsToMarkers.java:147)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2333)
at org.eclipse.lsp4e.operations.diagnostics.LSPDiagnosticsToMarkers.updateMarkers(LSPDiagnosticsToMarkers.java:162)
at org.eclipse.lsp4e.operations.diagnostics.LSPDiagnosticsToMarkers.accept(LSPDiagnosticsToMarkers.java:83)
at org.eclipse.lsp4e.LanguageClientImpl.publishDiagnostics(LanguageClientImpl.java:74)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
at org.eclipse.lsp4j.jsonrpc.services.GenericEndpoint.lambda$null$0(GenericEndpoint.java:65)
at org.eclipse.lsp4j.jsonrpc.services.GenericEndpoint.notify(GenericEndpoint.java:152)
at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.handleNotification(RemoteEndpoint.java:220)
at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.consume(RemoteEndpoint.java:187)
at org.eclipse.lsp4e.LanguageServerWrapper.lambda$4(LanguageServerWrapper.java:260)
at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.handleMessage(StreamMessageProducer.java:194)
at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.listen(StreamMessageProducer.java:94)
at org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor.run(ConcurrentMessageProcessor.java:113)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630)
at java.base/java.lang.Thread.run(Thread.java:831)

[Updated on: Mon, 21 June 2021 12:05] by Moderator

Re: Eclipse 2021-06 error on maven pom [message #1842494 is a reply to message #1842490] Mon, 21 June 2021 12:52 Go to previous message
Eclipse UserFriend
Maybe you can ask about it here:

https://github.com/eclipse-m2e/m2e-core/issues

Are you running the IDE with Java 16?
Previous Topic:Egit and Switching Between Master and Branch
Next Topic:Content Assist
Goto Forum:
  


Current Time: Sun Aug 31 02:51:17 EDT 2025

Powered by FUDForum. Page generated in 0.26347 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top