Community
Participate
Working Groups
Shouldn't for a Java 9+ module project the project's build path be just a list of jars (and their paths in the workspace or local file system) and not decide about classpath or module path? Currently the build path (split up in Module and Class Path) is redundant, if a module-info exists. The rule would be as follows. * Build path lists all projects, jars and libraries to be available for classpath or module path. Basically the same dialog as currently for a non module project. * If no module-info exists in the project, all entries from the build path are put on the class path. * All modules (auto or not) required in module-info are put on the module path. All remaining on the classpath. The build path dialog could show, what entries are for the classpath and what for the module path to avoid confusion.
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.
