Community
Participate
Working Groups
Checking validity of an IModuleDescription for an auto module has some surprises: Auto modules never exists() because it cannot find an element info (since this thing is purely synthetic). If some build path references a project root as a class folder (see bug 546877) then asking for its auto module will return a handle where getElementName() returns "" (because an library IPackageFragmentRoot pointing to a project has no name). Also: In the situation of bug 546877, if both projects have module-info and B/src/module-info.java says "requires A", then this resolves to the *automatic* module A, although no automatic module with that name exists. At least the case of an auto module with empty name should be avoided, I believe. Maybe AutoModule.exists() should answer !this.name.isEmpty() (e.g., all auto modules with a valid name exist).
Bulk move out of 4.13
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.
