Re: [cross-project-issues-dev] org.eclipse.jdt.core from objectteams get

[Doug Schaefer <dschaefer@xxxxxxx>]

Yeah, I think we're OK since we depend on the eclipse.sdk feature which brings in the right version of JDT. I just saw OTDT fly by with another error message, but that seemed unrelated and is now gone.

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

________________________________________
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [cross-project-issues-dev-bounces@xxxxxxxxxxx] on behalf of Igor Fedorenko [igor@xxxxxxxxxxxxxx]
Sent: Friday, June 27, 2014 10:35 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

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

http://ci.tesla.io:8080/view/m2e/job/m2eclipse-core/

--
Regards,
Igor

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.
>
> /max
>
>>
>> Doug
>>
>> ________________________________
>> 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.
>> https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/updates/requirements/luna/build.xml#L32
>>
>>
>> HTH
>> --
>> Mickael Istria
>> Eclipse developer at JBoss, by Red Hat<http://www.jboss.org/tools>
>> My blog<http://mickaelistria.wordpress.com> - My
>> Tweets<http://twitter.com/mickaelistria>
>> _______________________________________________
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
> /max
> http://about.me/maxandersen
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev