Community
Participate
Working Groups
As stated in bug 538159, I experiment with Java 9 modules. I have a working set of 14 Java projects (all working well since years). I already chnaged the classpaths for the projects to avoid the Java 9 "--add-modules=ALL" workaround. So the current state is, I can compile with compiler compliance level 9. So far, so good. The I started to add a module-info.java to 1 of these projects and try to get the project compiled - without success. After my tests, I just remove the single module-info.java and the building hell begins: all projects are marked with a red icon with hundreds of problems. I still have no idea in what order I have to refersh/built/clean project the single projects as my logical order of the technical dependencies doesn't help. The projects within the working set all depend on each other (except 1 basic project). They point to each other by their "Java Build Path" > Projects, i.e. the Eclipse projects are referenced. It takes about 10 to 20 minutes to "wildly" refresh/build single /build all / clean project / clean all projects until somewhen all problems vanished. Perhaps a "order" of the projects withint the workingset could help (which is not possible now). And only eclipse internal knows when to refresh/built/clean the single projects. So, at least please offer an order of projects within a working set.
... perhaps a hint: after added module-info.java, Eclipse somehow moves all the Jars to module path. After removing module-info.java, this classpath change stays the same (misc "module" lines in .classpath).
Sarika, do you think we should consider moving the jars back to classpath if the project is not modular?
(In reply to Jay Arthanareeswaran from comment #2) > Sarika, do you think we should consider moving the jars back to classpath if > the project is not modular? I think it is still in compiler scope and not reached launch configuration level.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
