ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sebastian Krueger <>
Subject Compiling Eclipse Plugin with Ivy [OSGI] (Package capability version not resolved correctly)
Date Fri, 06 Jan 2012 02:15:32 GMT

I've come across a lot of blocking issues when compiling even the
simplest HelloWorld Eclipse plugin with Ivy [trunk]. See: IVY-1329,
IVY-1330. More bug fixes/reports to come in the next few days.

So I'm wondering if there is anyone out there who uses this feature at all.

It's mostly working now after tweaking the OSGI code in various
places. But I'm stuck on something that I'm not sure how to attack.

After generating the OBR XML there are two bundles which look
something like the following:

repo-eclipse.xml (generated using a fixed version of the
eclipse-plugin example ivy project):
<resource symbolicname="org.eclipse.equinox.common" version="3.6.0.v20110523"
		<require name="package"
<resource symbolicname="org.eclipse.osgi" version="3.7.0.v20110613"
		<capability name="package">
			<p n="package" v="org.eclipse.equinox.log" />
			<p n="version" v="1.0.0" />

The issue here is that Ivy will throw the following error:
eclipse: unacceptable revision => was=3.7.0.v20110613 required=[1.0.0,2.0.0)
org.eclipse.equinox.common requires org.eclipse.equinox.log version
[1.0.0,2.0.0) but seems to only find version 3.7.0.v20110613.

The bug appears to be that when resolving package capabilities in the
OBR XML the require is compared to the resource/@version and not the

The issue goes away if I manually edit the generated OBR XML and
change the version to 3.7 for the package capability. However, it
would be better if the resolver code would actually resolve this one

Has anyone got a view on how to fix this, or some advice on how they
use Ivy to build Eclipse plugins (without hacking the OBR XML code).



To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message