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

looks similar to


I've seen the same problem with tycho builds against Luna RC4 repo (OTDT version of org.eclipse.jdt.core bundle being selected by the p2 resolver instead of the original one)


workaround for tycho builds is to filter out the OTDT bundle version from the target platform

(or use .target file with perfect version matches)


My impression is it's up to p2 resolver implementation details which solution is chosen, so depending on the overall bundles being resolved, either the solution using OTDT or original may be chosen.









From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Paul Webster
Sent: Mittwoch, 25. Juni 2014 01:44
To: Cross project issues
Subject: Re: [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 <thomas@xxxxxxx> 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 higher version (3.10.0.v_OTDT_r230_201406101339) than the one found in the platform repo (3.9.2.v20140114-1555).


I don't know what's causing it, but the staging repo doesn't have that version of jdt.core:
pwebster@build:/home/data/httpd/> ls plugins/org.eclipse.jdt.core_*

None of the eclipse/updates/4.4* repos have 3.9.2 (which is Kepler SR2 I guess)  either.


Back to the top