eclipse-jdt / eclipse-jdt/eclipse.jdt.core
Eclipse not compiling code, only module-info and not showing any errors
- Dominant language
- Java
- Stars
- 237
- Forks
- 195
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 47
Description
I work on a large project that consists of a large number of modules. The structure is roughly like follows:
Project (module) A
Project (module) B that depends on A
Projects (modules) C1, ..., Cn that all depend on B
So all these C projects depend transitively on A but they are NOT using directly code from it.
When I defined the C projects, I only added the direct dependency B to it. This has been working fine for years.
But at some time I wasn't able to run my program any more, I just got an exception of a missing service (to be exported by C).
Turned out that the service implementation was actually missing, the Eclipse compiler built only the module-info for it,
created the package directories but it did not compile any of the modules classes. After adding the transitive dependency,
everything worked as it should.
I've got now projects without the added transitive dependency and some with it, so this seems to be an intermittent issue, hard to reproduce. All projects get compiled perfectly fine, albeit the difference. I assumed, Eclipse would find those transitive dependencies.
The bug however is, that the compiler clearly fails but no error or exception whatsoever is shown on the UI. It took me a lot of digging
to figure out what the issue is. I did a build on these projects one by one, they fail but the problems panel shows
0 errors, n warnings, m others.
There seems to be no way to show the compilers output directly.
Would be great if that could be fixed.
org.eclipse.jdt.core.javabuilder
org.eclipse.jdt.core.javanature
Eclipse IDE for Enterprise Java and Web Developers (includes Incubating components)
Version: 2025-03 (4.35.0)
Build id: 20250306-0812
PS: I accidentally reported it in the wrong place before: https://github.com/eclipse-platform/eclipse.platform/issues/2091
Contributor guide
Assessment
This issue has not been assessed yet.