Community
Participate
Working Groups
This is an Organizational Collection of Issues This Issue "depends on" several related Issues. Use "Show dependency tree" to get an overview of the related Issues. Please comment whenever possible within the related Issues.
can someone please complete the entries, as I'm not familar which further JSR are relevant. The goal is to have a clear dependency tree: https://bugs.eclipse.org/bugs/showdependencytree.cgi?id=80775
What are you trying to achieve here ? If you found issues about our support of J2SE 5.0 features, please rather enter specific bugs. If you are trying to understand where we are at, please rather indirect through JDT forum, or ask questions in bug 36938 (where I just commented that we had support for all required features).
I've documented what I try to achieve here [abstract: using the dependency tree to increase transparency and clarity, thus users which are intrested just in "JSR175 metadata" do not have to fight through the jungle of information within Bug 36938]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=36938#c116 Additionally, this Issue here subjects "100% jck1.5 compliance", thus it will be RESOLVED when all 11331 tests you've mentioned pass: https://bugs.eclipse.org/bugs/show_bug.cgi?id=36938#c115 bug 36938 is overloaded with information and the Issue-Tracking-System should clarify the status without the need to ask on the JDT forum. Please do not resolve this Issue before the "100% jck1.5 compliance" is reached. [I'll try to create the further entries to a later point, thus any user (or potential user) can see immediatly the precise status of the 1.5 functionality of his interest ]
Bug 36938 is the one we will close once we reach 100% compliance, but not only that, entire 1.5 support throughout the board on JDT/Core, which means more than just the compiler (biggest piece though). As to having individual bugs for recording intermediate steps, this is fine, but you should rather associate them to the master bug 36938 rather than spawning another thread, and add more confusion. Also the JDT/Core web page reflects the status of progress on 1.5 front in a synthetic way.
Lets agree [provisional] that this Issue here is about the _compiler_ [btw: the compiler should be an seperate component]. [sidenote: precisely, Bug 36938 "Add early support for J2SE 1.5 features" is an past issue, as the J2SE is 1.5 already released. "early support" and "support" are two different issues.] I'll create the dependency-tree within this Issue, to avoid the large amount of email-traffic generated on Bug 36938 (which has many CC's / voters). Please have a little trust and patience. I assure you that this here will increase clarity when finished. [note: JDT/Core web page: see the Field "URL" (above "Summary") in the header of this Issue]
Bug 36938 is not a separate issue. It represents exactly what we are trying to achieve for R3.1. I am only seeing this current bug as a progress report, which will soon get closed as we reduced our last JCK issues. Out of curiosity, can you document about jck failures ?
Comment 6: With all respect: Bug 36938 can serve as a nice showcase of how to _not_ use an issue-tracking-system like Bugzilla. but ok, so lets take this bug here as a status-report [please report the current jck-failures and other deficits in the related bugs]. jck failures: sorry, but I cannot document about them at this moment.
Bug 36938 exists for historical reasons, and is used as some sort of newsletter to announce progress on 1.5 front. It existed before 3.1 was planned. Why do you think we need this extra bug then if you cannot provide material on JCK compliance front ? Are you trying to teach us how to develop our compiler technology ? If so, why didn't you interact on JDT forums explaining what you are trying to achieve before starting tampering in our inbox ?
I don't want to annoy the developers on the dev-lists. Once more I ask you to have a little trust and patience. If you like to discuss this further, please use the following thread withing eclipse.foundation newsgroup: http://www.eclipse.org/newsportal/article.php?id=202&group=eclipse.foundation
For the last time, I ask you to be more specific in your PRs. The J2SE 5.0 features are implemented, and you arrive after the battle. For that matter, I will close again all these defects (I am the component owner) unless they become more specific (pls adjust title to reflect real issues). The plan you keep referring to is being updated by us, and does not need to be echoed into bugzilla. Bugzilla is meant to track bugs. Some missing features are not omissions, they are simply things which we are going to address next. Entering specific PRs to help us address the last issues is valuable, and all other reporters are doing so, and we are grateful for their findings.
"The J2SE 5.0 features are implemented" => they are not, according to the status report. "pls adjust title to reflect real issues" => Should I really add the word "Missing" before the Subjects? Your status-report is not automated and it was not up-to-date: * https://bugs.eclipse.org/bugs/show_bug.cgi?id=81471#c3 * The report is still missleading. You should _really_ have the gentleness to enter the specific information about the status within bugzilla, thus any user finds the information immediately. Bugzilla is an Issue-Trackin-System, which is not just limited to Bugs. Once more I ask you friendly to comment about the general project-resource usage within the opened thread in the eclipse.foundation newsgroup: http://www.eclipse.org/newsportal/article.php?id=202&group=eclipse.foundation You may be the component-lead, but this here is not your personal playground - you are obligued to stay in-context / in-topic. I expect a little more respect for my efforts, even if they are inconventional. So _please_ report the status precisely within the depending bugs (or point me to a _precise_ status, thus I can enter it myself).
Had your initiative occurred 6 months ago, I would have found it valuable since reporting progress on 1.5 front is time consuming given the multiplicity of channels we use. But now, your PRs are annoying us, since they look not specific enough given the amount of work we accomplished already. So as to keep the community informed of our progress, we will keep updating bug 36938. If you want to maintain your tree dependencies, this is up to you, but unless the community would listen to it, we will not update it by ourselves, other than closing them once we have 1.5 support across the board. Changing title to remove licensed material mention.
thank you for your comments and corrections.
Closed as redundant based on bug 36938 (not tagging as dup to avoid unnecessary spam to master bug)
this issue is not a duplicate of bug 36938 "[plan item][1.5] Add early support for J2SE 1.5 features" which essentially subjects "Cheetah" early support for eclipse 3.0 thus it is not redundant. dependend JSR's added. 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
