Community
Participate
Working Groups
EMF autogenerates significant contributions to user plugins, but unfortunately these do not play well with API tooling. By itself, EMF autogeneration is seriously incompatible, but EMF permits "@noreference" etc to be embedded in persisted 'user comments', thereby giving some prospect of utility. When an EMF model grows it adds definitions that should be all resolveable by @since... but Problem 1: EMF adds definitions with a nested Literals class. Bug. API Tooling ignores @noreference etc on nested classes. Problem 2: EMF defines many integer constants which the users is encouraged to reference symbolically. These constants are unstable. API tooling offers no @noreferenceByValue allowing safe access by symbol.
(In reply to Ed Willink from comment #0) > Problem 2: EMF defines many integer constants which the users is encouraged > to reference symbolically. These constants are unstable. API tooling offers > no @noreferenceByValue allowing safe access by symbol. Bug 543621 outlines a rather simple change to EMF auto-generation that avoids publishing unstable integers.
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.
It is a hard but very genuine problem. Cannot be stale until reviewed by a relevant committer.
