| Summary: | The package org.eclipse.core.runtime is accessible from more than one module | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Markus S <liedrig> |
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
| Status: | CLOSED INVALID | QA Contact: | |
| Severity: | blocker | ||
| Priority: | P3 | CC: | jjohnstn, rbnn, tjwatson |
| Version: | 4.22 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 10 | ||
| Whiteboard: | |||
|
Description
Markus S
(In reply to Markus S from comment #0) > Hi, > > I'm getting all the fun of migrating the target platform of our application > from Java8 / Eclipse 4.4 to Java11 / Eclipse 4.22, but I'm getting these > errors all over the place: > Is this errors in your workspace while compiling your code or errors at runtime when running on Java 11? This happens already while compiling the code (In reply to Markus S from comment #2) > This happens already while compiling the code Moving to JDT for comment. Moving to core I'm trying to use JDK 17 now (which I also use to start my IDE) and I get a different error now:
> Multiple markers at this line
> - The type java.lang.String cannot be resolved. It is indirectly referenced from required .class files
> - Type java.lang.String is indirectly referenced from required .class files but cannot be resolved since the declaring package java.lang exported from module java.base conflicts with a package accessible from module <unnamed>
I took out some plugins that came with the Eclipse 4.22 SDK and the error is gone. Still not sure if I did something wrong, but I'm good for now. (In reply to Markus S from comment #6) > I took out some plugins that came with the Eclipse 4.22 SDK and the error is > gone. Still not sure if I did something wrong, but I'm good for now. What were those plugins? And how did you get rid of them? |