Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 535930

Summary:	module-info.java are read even if excluded from the build path
Product:	[Eclipse Project] JDT	Reporter:	Rémi Forax <forax>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	CLOSED MOVED	QA Contact:	Jay Arthanareeswaran <jarthana>
Severity:	normal
Priority:	P3	CC:	loskutov, manoj.palat
Version:	4.9
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description Rémi Forax

2018-06-15 05:23:23 EDT

A module-info.java can be excluded from the build path like any other resources, but in that case, Eclipse still read it and you can even see 2 items named module-info.java (the excluded resources and the normal resource).

If a module-info is excluded, it should not be taken into account by the JDT

Comment 1 Eclipse Genie

2020-07-03 19:59:15 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 2 Rémi Forax

2020-11-20 02:46:53 EST

Bug still there.

You can not use Eclipse with a separate module-info for sources and tests.
The module-info.java for the test being excluded. 

And you need that by example when you have modular integration tests
See https://sormuras.github.io/blog/2018-09-11-testing-in-the-modular-world.html

Comment 3 Jay Arthanareeswaran

2021-03-04 02:20:15 EST

Sorry, haven't had a chance to look at this. Moving out of 4.19.

Comment 4 Eclipse Genie

2023-03-08 07:36:24 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 Rémi Forax

2023-03-08 07:45:31 EST

The issue still exist and have not been fixed.

Comment 6 Andrey Loskutov

2023-03-09 08:24:12 EST

(In reply to Rémi Forax from comment #5)
> The issue still exist and have not been fixed.

Remi, the project bug tracker is moved to https://github.com/eclipse-jdt/eclipse.jdt.core/issues.

Can you please submit a bug there, ideally with a simple project demonstrating the problem? Thanks.