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

FWIW, we build m2e against simrel repository and don't have any problems.


On 2014-06-27, 10:27, Max Rydahl Andersen wrote:
On 26 Jun 2014, at 10:49, Doug Schaefer wrote:

We build directly against the Eclipse one. Does that mean we can't do
that any more?

you haven't been able to do that for ~2 years.

Michael - do you recall why ODT keeps getting be allowed in the release
train ? Thought we opened a bugzilla on this a while back since
it really does not seem sane a plugin on the release train is allowed to
"mutate" one of the plugins.



From: cross-project-issues-dev-bounces@xxxxxxxxxxx
[cross-project-issues-dev-bounces@xxxxxxxxxxx] on behalf of Mickael
Istria [mistria@xxxxxxxxxx]
Sent: Thursday, June 26, 2014 10:45 AM
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/26/2014 04:42 PM, Doug Schaefer wrote:

I just noticed this in our product builds now too. What was the
solution? I imagine this is going to affect everyone that includes JDT
in their product, no?

FYI, for JBoss Tools and JBoss Developer Studio, we do have a mirror
of the Luna repository from where we explicitly exclude the OTDT
patch. And since we consume this repository, we are sure we always get
the JDT one.

Mickael Istria
Eclipse developer at JBoss, by Red Hat<>
My blog<> - My
cross-project-issues-dev mailing list

cross-project-issues-dev mailing list

Back to the top