Community
Participate
Working Groups
Implement the JSR-175 metadata facility.
Annotation support got released to HEAD recently, and will be part of R3.1 milestone-4 delivery.
" metadata facility (jsr-175) (1 month) * coming soon : detection of circular annotations " source: http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-core-home/r3.1/main.html According to the (just updated) plan, this Issue is still open. I just reopen this issue here [without opening a seperate Issue on the "circularity detection problem"]
.
Comment 3: Is this the way to implement 5.0 support into eclipse? Closing issues which are unique, valid and clearly _open_ with a remark "."? reopened & added depending bugs.
I've removed dependency to bug 81498 because last missing point for annotation (circular annotation not detected) in 3.1 M4 does not block bug 81498 implementation. IMO and _according_ to the (just updated) plan, this bug 80776 should have a summary like: "[1.5][annot] Circular annotations are not detected". This would be a better unique, valid and clearly open issue which surely gets everybody's agreement and never be closed until it is effectively fixed.
Since the only real issue here detecting circular annotations, we will track the problem in bug 81974. There is no need for 2 PRs. *** This bug has been marked as a duplicate of 81974 ***
No duplicate relation to Bug 81974, but a "depends on" relation. reopened. - JSR-175 Metadata Facility (annotations) is not yet fully implemented within JDT.Core. This is an unique, valid and unresolved Issue. Resolving this Issue depends on Bug 81974 (as entered).
Comment 5: This Issue affects the overall "JSR-175 Metadata..." implementation in JDT.Core. Bug 81498 was entered as a "depending on" (not as "blocks", as you've stated). Without solving Bug 81498, Bug 81366 cannot be solved: "The AllTypesCache does not know about Enums and Annotations. Therefore, the Open Type dialog shows wrong icons for Annotations (e.g. SuppressWarnings) and Enums (e.g. Thread.State)." It seems to me, like without the above functionality, one cannot assert that "JSR-175 Metadata..." is implemented fully withing JDT.Core. If I assume correct, please reenter Bug 81498 withing the "depends on" field.
You're not correct regarding our bugs reporting tool Bugzilla. When you put a bug dependent to another one, then that means that its resolution is blocked until the other bug is fixed. "Blocks" is the reciproque relation of "Depends on" (look at the beginning of each bug report). As bug 80776 is not enough precise, it is wrong _and_ confusing to say that it blocks bug 81498... In fact, I would say that this is bug 80776 which is confusing but it seems that you really do not want to understand it... (Note that I did not remove dependency to bug 81366 as it is really blocked by it...)
Since its abundantly clear from your behaviour that you have no interest in reporting & helping solve problems, this will be the last time we bother to respond. From now on, we'll just close PRs that have no value.
Comment 10: you rating "of no value" has no relevance within this open-source project. Your comments and responses become more and more irrelevant to me, as they are obvisously not driven by rationality or by the will to provide full issue transparency to the user base (here: about the "1.5 support" implemenation status). If an issue is valid, unique and unresolved, you have _no_ right to close it whilst using any personal twisted views that you apply. Further remarks within Comment 7.
Comment 9: My elaborations within Comment 8 remain valid (bug 81498 seems to block bug 80776, Implementing JSR-175 within JDT.Core). - I have understood the dependency feature, whith which i've created this dependency-tree: https://bugs.eclipse.org/bugs/showdependencytree.cgi?id=80775 which your team-fellow disrupts continously, whils resolving the issues. Thus, if you like to explain it, please explain it to Mr. Kent Johnson, who becomes more and more annoying whilst using this resourse like his personal sandbox.
reopened
JSR-175 Metadata Facility is not yet fully implemented within JDT.Core. Reopened.
Its impossible to say when we're 100% bug free, so moving to REMIND. Its up to the super human intelligent one amongst us to close in the future.
GC
