Problem using eclemma with Eclipse 4.4.2 (uses conflict on ASM)

[duft....@gmail.com]

Hey,

I tried upgrading our Eclipse to 4.4.2 release, which gives me this error:

!ENTRY org.eclipse.pde.api.tools 4 0 2015-03-05 07:53:38.385
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.pde.api.tools [1543]
Bundle was not resolved because of a uses contraint violation.
org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.pde.api.tools [osgi.identity; osgi.identity="org.eclipse.pde.api.tools"; type="osgi.bundle"; version:Version="1.0.600.v20140520-1809"; singleton:="true"] because it is exposed to package 'org.objectweb.asm' from resources org.objectweb.asm [osgi.identity; osgi.identity="org.objectweb.asm"; type="osgi.bundle"; version:Version="5.0.1.v201404251740"] and com.mountainminds.eclemma.asm [osgi.identity; osgi.identity="com.mountainminds.eclemma.asm"; type="osgi.bundle"; version:Version="2.3.2.201409141915"] via two dependency chains.

Chain 1:
org.eclipse.pde.api.tools [osgi.identity; osgi.identity="org.eclipse.pde.api.tools"; type="osgi.bundle"; version:Version="1.0.600.v20140520-1809"; singleton:="true"]
require: (&(osgi.wiring.bundle=org.objectweb.asm)(&(bundle-version>=5.0.1)(!(bundle-version>=6.0.0))))
|
provide: osgi.wiring.bundle: org.objectweb.asm
org.objectweb.asm [osgi.identity; osgi.identity="org.objectweb.asm"; type="osgi.bundle"; version:Version="5.0.1.v201404251740"]

Chain 2:
org.eclipse.pde.api.tools [osgi.identity; osgi.identity="org.eclipse.pde.api.tools"; type="osgi.bundle"; version:Version="1.0.600.v20140520-1809"; singleton:="true"]
require: (&(osgi.wiring.bundle=org.objectweb.asm.tree)(&(bundle-version>=5.0.1)(!(bundle-version>=6.0.0))))
|
provide: osgi.wiring.bundle; bundle-version:Version="5.0.1.v201404251740"; osgi.wiring.bundle="org.objectweb.asm.tree"
org.objectweb.asm.tree [osgi.identity; osgi.identity="org.objectweb.asm.tree"; type="osgi.bundle"; version:Version="5.0.1.v201404251740"]
import: (osgi.wiring.package=org.objectweb.asm)
|
export: osgi.wiring.package: org.objectweb.asm
com.mountainminds.eclemma.asm [osgi.identity; osgi.identity="com.mountainminds.eclemma.asm"; type="osgi.bundle"; version:Version="2.3.2.201409141915"]
at org.eclipse.osgi.container.Module.start(Module.java:434)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)


It looks like eclemma is exporting an old objectweb ASM version? Somehow this conflicts with the new ASM required by pde.api.tools. It looks like asm.tree imports the asm package without version (.... pfff....) and catches the one from eclemma. Is this export really required? Can't eclemma use a dependency to recent ASM?

Thanks in advance for any help and/or ideas :)

Cheers,
Markus

[duft....@gmail.com]

Sorry, forgot to mention: old eclipse version was 4.4.1, so not a really major upgrade :)

[Marc Hoffmann]

What Eclipse package are you using?

Regards,
-marc

> --
> You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jacoco+un...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/b0265038-a6b0-4402-a281-9170c3e73002%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[duft....@gmail.com]

Interestingly this only seems to happen if i try to start a debugable Eclipse in that platform. As soon as everything is rolled out to a "real" standalone Eclipse, things seem to work....

[Marc Hoffmann]

Hi,

as ASM is not available with all Eclipse distributions, especially not
in the latest version.

JaCoCo comes with the bundle com.mountainminds.eclemma.asm which exports
ASM packages in version 5.0.1 (the latest release as of today). Maybe
one of the ASM dependent bundles does not specify proper upper version
bounds?

Regards,
-marc

[duft....@gmail.com]

Hey.

We're using Secure Delivery Center to pack together a custom Eclipse package. It's based on the "standard" package however, adding quite a lot of stuff (xtext, PDE, emf, ...).

Wrong version boundaries might be. What's worrying me a little is that it did not work when I tried it first, but now the problem seems to have disappeared - maybe there was some old artifact in some PDE cache still...? I don't know. I think there is no need to investigate more right now - maybe if it happens again.

Still thanks for the prompt reply and help!

BR, Markus