Istria [mist...@redhat.com]
Sent: Thursday, June 26, 2014 10:45 AM
To: cross-project-issues-dev@eclipse.org
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
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
AM
To: cross-project-issues-dev@eclipse.org
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
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
[stephan.herrm...@berlin.de]
Sent: Friday, June 27, 2014 12:16 PM
To: cross-project-issues-dev@eclipse.org
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
Hi Doug,
On 06/27/2014 06:36 PM, Doug Schaefer wrote:
I guess the real question, is that if someone ends up with the
OTDT version of the JDT, do bad things happen?
JDT has occasionally received a bug report that was actually a bug in OTDT.
The same happens with Groovy as well. From memory I'd
: [cross-project-issues-dev] org.eclipse.jdt.core from objectteams
gets selected due to higher version
On Tue, Jun 24, 2014 at 6:09 PM, Thomas Hallgren
tho...@tada.semailto:tho...@tada.se wrote:
I just encountered a build failure when using the platform repository in
conjunction with the luna
On 06/25/2014 12:09 AM, Thomas Hallgren wrote:
I just encountered a build failure when using the platform repository in
conjunction with the luna staging one. The failure was
caused by p2 preferring the objectteams patch for org.eclipse.jdt.core in favor
of the original. Seems the patch has a
On 2014-06-25 12:57, Stephan Herrmann wrote:
Can you share a setup for reproduction?
The reference to 3.9.2... looks fishy, indeed.
The reference to 3.9.2 was introduced when I tried to fix the problem and appointed the wrong platform site. My error.
Please disregard that. The real problem
My guess is that the reason it gets selected by p2 is that the version
3.10.0.v_OTDT_r230_201406101339
is lexically greater than
3.10.0.v20140604-1726
since '_' (0x5f) is greater than '2' (0x32)
- thomas
On 2014-06-25 12:57, Stephan Herrmann wrote:
On 06/25/2014 12:09 AM, Thomas
Correction. Should say selected by Buckminster, not selected by p2 since this isn't a build-time best-effort
resolution and not a full p2 resolution. I guess the same can be said about the Tycho resolution.
- thomas
On 2014-06-25 14:17, Thomas Hallgren wrote:
My guess is that the reason it
On 06/25/2014 02:17 PM, Thomas Hallgren wrote:
My guess is that the reason it gets selected by p2 is that the version
3.10.0.v_OTDT_r230_201406101339
is lexically greater than
3.10.0.v20140604-1726
since '_' (0x5f) is greater than '2' (0x32)
This is intended and required to make the
I just encountered a build failure when using the platform repository in conjunction with the luna staging one. The
failure was caused by p2 preferring the objectteams patch for org.eclipse.jdt.core in favor of the original. Seems the
patch has a higher version (3.10.0.v_OTDT_r230_201406101339)
On Tue, Jun 24, 2014 at 6:09 PM, Thomas Hallgren tho...@tada.se wrote:
I just encountered a build failure when using the platform repository in
conjunction with the luna staging one. The failure was caused by p2
preferring the objectteams patch for org.eclipse.jdt.core in favor of the
14 matches
Mail list logo