Community
Participate
Working Groups
ModuleDeclaration.analyseModuleGraph(CompilationUnitScope) may not detect that a required SourceModuleBinding is deprecated, because ensureAnnotationsResolved() may not have run at that point in time. To wit: use Deprecated9Test.testBug533063_2() (as proposed via https://git.eclipse.org/r/#/c/132799/) remove the line this.moduleMap.clear() and watch the test fail. Insert requiredModule.getAnnotationTagBits() before asking isDeprecated() and see it pass again. Could such a call influence compilation order in unwanted ways? In fact, SourceModuleBinding.isDeprecated() may want to call ensureAnnotationsResolved() for good measure.
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.
