Bug 535929 - Support Module path folder
Summary: Support Module path folder
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.9   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-15 05:20 EDT by Rémi Forax CLA
Modified: 2022-10-03 17:20 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rémi Forax CLA 2018-06-15 05:20:11 EDT
Unlike the classpath, the module path allow you to specify a folder and the complier/VM will find the modules by name in the folder.

As far as i know there is no way to specify such folder when configuring the module path using the Eclipse JDT.
Comment 1 Stephan Herrmann CLA 2018-06-15 14:56:11 EDT
Is this about the batch compiler or build paths in the IDE?
Comment 2 Rémi Forax CLA 2018-06-16 06:23:38 EDT
The IDE, the .classpath and the corresponding UI if you prefer,
as far as i remember, ecj already support specifying folders in --module-path.
Comment 3 Stephan Herrmann CLA 2018-06-16 07:34:49 EDT
Thanks for clarification.

Firstly, I don't think there is a specification requiring IDEs to support his, is there? While I'm at it, is there an up-to-date version of JEP 261 somewhere on the net? Some time ago I was informed that the original JEP information is outdated, so it is impossible for us to know whether JDT supports all that is required.

As for the request itself, I see it as a corner case, as modules developed within Eclipse have a different layout, viz. one module per project, so it is more like projectx/src/... rather than src/modulex/...

Still, for externally developed modules there _could_ be use cases where an Eclipse project should refer to a classes/modulex/... structure. I'm not sure how relevant this is, though, because externally developed modules should normally be consumed from their jar, not a class folder (class folders are not for publishing an artifact). But since Eclipse does support external class folders, supporting the new layout could be seen as consistent with the existing design.

IMHO, not a high priority, though. Let me know if you see reasons, why this is practically relevant.
Comment 4 Rémi Forax CLA 2018-06-17 05:31:13 EDT
my request has nothing to do with a source layout, this is another discussion.

currently, when i specify a module-path, i can specify external dependencies, by example jars that comes from Maven by indicating the folder that contains all the jars instead of specifying the jars one by one like i need to do with the classpath.

what i think eclipse should be able to provide is something that let me say, here is a folder that will contains jars, use the module-info to find the ones that are available for that module.

obviously i should be able to to provide several folders and eclipse should mimick the way the default ModuleFinder works.
Comment 5 Eclipse Genie CLA 2020-07-06 16:20:52 EDT
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.
Comment 6 Eclipse Genie CLA 2022-10-03 17:20:18 EDT
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.