Bug 540327 - [9] Report when module-info.java is not in the root of a source folder
Summary: [9] Report when module-info.java is not in the root of a source folder
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.9   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-19 17:30 EDT by Stephan Herrmann CLA
Modified: 2023-03-23 09:05 EDT (History)
3 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 Stephan Herrmann CLA 2018-10-19 17:30:56 EDT 
It seems that in bug 539458 confusion was caused by a module-info.java sitting in a sub-directory of a source folder.

We should raise a warning (error?) to inform the user about it.
Comment 1 Andrey Loskutov CLA 2018-10-19 17:53:31 EDT 
Error would be better. I've seen workspaces with ~60000 warnings, one would never find another one there. But this check should be for 1.9 and higher projects only.
Comment 2 Jay Arthanareeswaran CLA 2018-11-27 01:19:25 EST 
Stephan,

Are you still considering this for 4.10? Doesn't sound that critical to me.
Comment 3 Manoj N Palat CLA 2019-02-11 04:06:11 EST 
Bulk move out of 4.11
Comment 4 Eclipse Genie CLA 2021-02-01 03:45:04 EST 
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 5 Eclipse Genie CLA 2023-03-23 09:05:36 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.