Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] org.eclipse.jdt.core from objectteams gets selected due to higher version

No one doubts your commitment to JDT. You've been great helping them out. And we all appreciate that.

I guess the real question, is that if someone ends up with the OTDT version of the JDT, do bad things happen? I agree you followed all that was asked of you, but I think we assumed and I do hope you've accomplished what's best for the community at large. What were the plans to mitigate these issues?


From: cross-project-issues-dev-bounces@xxxxxxxxxxx [cross-project-issues-dev-bounces@xxxxxxxxxxx] on behalf of Stephan Herrmann [stephan.herrmann@xxxxxxxxx]
Sent: Friday, June 27, 2014 12:16 PM
To: cross-project-issues-dev@xxxxxxxxxxx
Subject: Re: [cross-project-issues-dev] org.eclipse.jdt.core from objectteams gets selected due to higher version

On 06/27/2014 05:34 PM, Doug Schaefer wrote:
> But I do remember a lot of concern when this came along and Max's question is a valid one to ask. We do have two JDT's in the simrel repo. That's pretty scary.
> Doug

OK, I had to dig 3+ years into the past to find the original agreement.
Here are the main references for your convenience:

The general case was discussed in this bug:
Conclusion: no new rules needed for such a rare situation.
The special case should be handled via a request for exception.

Request for exception was raised via tools PMC:

The result was to make the decision depend on an agreement
between JDT and Object Teams. This reflects the discussion in
both tools PMC and Planning Council.

This agreement has been achieved in a phone call between Dani
and myself. After that call, I brought the request to the
eclipse PMC:
In that thread you find Dani's confirmation, four +1 votes,
and no 0 or -1 votes.

Aside from formal process, need I assure anybody on this list,
how much I care about the quality and reputation of JDT?


cross-project-issues-dev mailing list

Back to the top