Bug 519206 - [9] Batch compiler should handle single module mode better
Summary: [9] Batch compiler should handle single module mode better
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.6   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Jay Arthanareeswaran CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-05 05:06 EDT by Jay Arthanareeswaran CLA
Modified: 2022-09-12 17:33 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jay Arthanareeswaran CLA 2017-07-05 05:06:29 EDT 
One can invoke the ECJ  (command line) in single module mode by simply supplying the module-info as one of the files to be compiled. However, the compiler is unable to cope with certain things in this mode. 

For e.g. compiling exports clause has issues. This is because we don't put any entry in FileSystem#moduleLocations for the module we are compiling. This results in module not being found in FileSystem#getModulesDeclaringPackage() - the else block.

Perhaps we should remember that we are in single module mode and simply assign that module to each CU.
Comment 1 Stephan Herrmann CLA 2017-07-11 14:17:22 EDT 
See bug 517808 comment #65
Comment 2 Manoj N Palat CLA 2018-05-21 06:22:52 EDT 
Bulk move out of 4.8

@Jay - retargetting to 4.9 - please modify the target as appropriate
Comment 3 Eclipse Genie CLA 2020-08-18 16:48:43 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 4 Eclipse Genie CLA 2022-09-12 17:33:54 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.