Community
Participate
Working Groups
As per Java9 module system implied readability, module B requires public A and module C requires B means, module C can see A without explicitly declaring dependency using requires in module C's module descriptor. Eclipse with Java9 support, resolves only explicit dependencies that are declared by a module using requires. Implicitly readable modules are not resolved. Will this be implemented? Tested with eclipse-SDK-Y20160908-1000-win32-x86_64
(In reply to Chandrakala MS from comment #0) > Will this be implemented? Of course. It is not clear why this scenario isn't working. We have a unit test for this: ModuleBuilderTests#test_ModuleSourcePath_implicitdeps() which is passing. But there's something fishy. It passes only when run as part of the suite. Fails only when that particular test is run. I will take a look.
(In reply to comment #1) > (In reply to Chandrakala MS from comment #0) > > Will this be implemented? > > Of course. It is not clear why this scenario isn't working. We have a unit test > for this: > > ModuleBuilderTests#test_ModuleSourcePath_implicitdeps() > > which is passing. But there's something fishy. It passes only when run as part > of the suite. Fails only when that particular test is run. I will take a look. Probably running into bug 499429 - there's a kind of chicken and egg situation where you need the package fragment roots initialized to know if a project is a module or not (the ModulePathContainer requires this information to figure out the dependencies), and you need the container to compute the package fragment roots. This leads to situations where things do not work reliably. I have a WIP patch that addresses this by making sure the module is initialized first before we try and compute the roots.
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.
