Community
Participate
Working Groups
BMB.cachePartsFrom() says // TODO(SHMOD): handle null case where a required module cannot be found. I guess for normal 'requires' this is game, but for 'requires transitive' we should really report an error. Since we have no source I suggest another kind of build path error. Null handling is also missing in resolvePackages() (both exports and opens). Since opens is not relevant for compilation we may ignore those, but an unresolved exports indicates a corrupt module and should also cause a built path error, IMHO. During work on bug 547114 I'm wondering if creating a marker on .classpath would be more suitable than on the project (it would be double-clickable), but then .classpath should really be hidden during normal use... Alternatively, JDT/UI could implement a navigation from the problem to the Java Build Path dialog.
New build path problems likely to be deferred to 4.13.
Bulk move to 4.14
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.
