Problem installing EclEmma and JBoss Tools Server Adapter

[phermsdorf]

Hi,

I'm aware that this is not actually a oomph issue, but maybe oomph can help to work around it ;)

When installing our IDE with oomph based on the Eclipe IDE for RCP and Rap Developers Product configuration (currently we use version 2025-03) you get the eclipse EclEmma plugin/feature installed.

We additionally install org.eclipse.jst.server_adapters.feature.feature.group and org.jboss.ide.eclipse.as.feature.feature.group from https://download.jboss.org/jbosstools/photon/stable/updates/ (which seems to be the latest version available).

After that when trying to add a Server configurations for Wildfly we see

instead of

and in the Eclipse log

!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.jboss.ide.eclipse.as.ui [850]
  Unresolved requirement: Require-Bundle: org.jboss.tools.as.runtimes.integration; bundle-version="[3.0.0,4.5.2)"
    -> Bundle-SymbolicName: org.jboss.tools.as.runtimes.integration; bundle-version="3.10.3.v20230714-1629"; singleton:="true"
       org.jboss.tools.as.runtimes.integration [856]
         Unresolved requirement: Require-Bundle: org.eclipse.datatools.connectivity; bundle-version="1.2.2"; resolution:="optional"
         Unresolved requirement: Require-Bundle: org.eclipse.datatools.connectivity.db.generic; bundle-version="1.0.1"; resolution:="optional"
         Unresolved requirement: Require-Bundle: org.jboss.tools.stacks.core; bundle-version="1.0.0"
           -> Bundle-SymbolicName: org.jboss.tools.stacks.core; bundle-version="1.4.300.v20230908-0745"
              org.jboss.tools.stacks.core [874]
                No resolution report for the bundle.  Bundle was not resolved because of a uses constraint violation.
  org.apache.felix.resolver.reason.ReasonException: Uses constraint violation. Unable to resolve resource org.jboss.tools.stacks.core [osgi.identity; type="osgi.bundle"; version:Version="1.4.300.v20230908-0745"; osgi.identity="org.jboss.tools.stacks.core"] because it is exposed to package 'org.apache.commons.logging' from resources org.apache.commons.logging [osgi.identity; type="osgi.bundle"; version:Version="1.2.0"; osgi.identity="org.apache.commons.logging"] and org.apache.commons.commons-logging [osgi.identity; type="osgi.bundle"; version:Version="1.3.5"; osgi.identity="org.apache.commons.commons-logging"] via two dependency chains.

Chain 1:
  org.jboss.tools.stacks.core [osgi.identity; type="osgi.bundle"; version:Version="1.4.300.v20230908-0745"; osgi.identity="org.jboss.tools.stacks.core"]
    require: (&(osgi.wiring.bundle=org.apache.commons.logging)(bundle-version>=1.1.1))
     |
    provide: osgi.wiring.bundle: org.apache.commons.logging
  org.apache.commons.logging [osgi.identity; type="osgi.bundle"; version:Version="1.2.0"; osgi.identity="org.apache.commons.logging"]

Chain 2:
  org.jboss.tools.stacks.core [osgi.identity; type="osgi.bundle"; version:Version="1.4.300.v20230908-0745"; osgi.identity="org.jboss.tools.stacks.core"]
    require: (osgi.wiring.bundle=org.apache.httpcomponents.httpclient)
     |
    provide: osgi.wiring.bundle; bundle-version:Version="4.5.14.v20230516-1249"; osgi.wiring.bundle="org.apache.httpcomponents.httpclient"
  org.apache.httpcomponents.httpclient [osgi.identity; type="osgi.bundle"; version:Version="4.5.14.v20230516-1249"; osgi.identity="org.apache.httpcomponents.httpclient"]
    import: (&(osgi.wiring.package=org.apache.commons.logging)(&(version>=1.2.0)(!(version>=2.0.0))))
     |
    export: osgi.wiring.package: org.apache.commons.logging
  org.apache.commons.commons-logging [osgi.identity; type="osgi.bundle"; version:Version="1.3.5"; osgi.identity="org.apache.commons.commons-logging"]
	at org.eclipse.osgi.container.Module.start(Module.java:495)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:2111)
	at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:146)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:2102)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:2044)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:2004)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1916)
	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:341)

!ENTRY ch.qos.logback.classic 1 0 2025-09-12 16:27:42.868

When uninstalling the EclEmma Feature the error is gone...

So there is a problem with org.apache.commons.commons-logging. Both of these bundles seem to require different (incompatbile) things from org.apache.commons.commons-logging .... i understand the actual problem only to a certain degree ...

My questions:

1. What is the actual problem?

2. On which side (EclEmma or JBoss Tools) should the problem be fixed? (and maybe how?)

3. is there a workaround, like "filtering out" the EclEmma feature while setting up the IDE Installation?

Thanks for any hints and ideas regarding this problem.

Bye Peter

[merks]

This just somehow seems familiar, like a bad fungus that's never really gone. I wonder if your problem is this problem again and if this is the workaround for it?

eclipse-orbit/orbit-simrel#40 (comment)

But it looks like you have the 1.3.5 and 1.2.0 versions.

But org.apache.httpcomponents.httpclient is is 4.5.14.v20230516-1249 which is actually older that this one:

So your problem might go away if you exclude that version (re-wrapped by old Orbit) and se the version without the qualifier (comes from Maven central as an OSGi bundle).

[merks]

Problems like this are a bit of nightmare. You really need to try out different things until one works. I suspect a likely solution is to avoid version 4.5.14.v20230516-1249 of org.apache.httpcomponents.httpclient (negative requirements) from being installed in favor of 4.5.14 (which is likely visible and available but p2 will text to pick the one with the highest version) because this is known to work in SimRel even with two logging bundles...

[phermsdorf]

I tried that and it "basically" works, but PDE tools and other stuff from the workbench stopped working with exceptions like this:

!MESSAGE The image could not be loaded: URLImageDescriptor(platform:/plugin/org.eclipse.jdt.ui/icons/full/obj16/jcu_obj.svg)
!STACK 0
org.eclipse.swt.SWTException: Unsupported or unrecognized format
	at org.eclipse.swt.SWT.error(SWT.java:4932)
	at org.eclipse.swt.SWT.error(SWT.java:4847)
	at org.eclipse.swt.SWT.error(SWT.java:4818)
	at org.eclipse.swt.internal.image.FileFormat.load(FileFormat.java:97)
	at org.eclipse.swt.graphics.ImageLoader.load(ImageLoader.java:154)
	at org.eclipse.swt.graphics.ImageDataLoader.load(ImageDataLoader.java:25)
	at org.eclipse.swt.graphics.ImageData.<init>(ImageData.java:334)
	at org.eclipse.jface.resource.URLImageDescriptor.getImageData(URLImageDescriptor.java:167)
	at org.eclipse.jface.resource.URLImageDescriptor.getImageData(URLImageDescriptor.java:143)
	at org.eclipse.jface.resource.URLImageDescriptor$URLImageDataProvider.getImageData(URLImageDescriptor.java:96)
	at org.eclipse.swt.internal.DPIUtil.lambda$2(DPIUtil.java:538)
	at org.eclipse.swt.internal.DPIUtil.getElementAtZoom(DPIUtil.java:567)
	at org.eclipse.swt.internal.DPIUtil.validateAndGetImageDataAtZoom(DPIUtil.java:538)
	at org.eclipse.swt.graphics.Image.<init>(Image.java:602)
	at org.eclipse.jface.resource.URLImageDescriptor.createImage(URLImageDescriptor.java:317)
	at org.eclipse.jface.resource.ImageDescriptor.createResource(ImageDescriptor.java:251)
	at org.eclipse.jface.resource.DeviceResourceManager.allocate(DeviceResourceManager.java:56)
	at org.eclipse.jface.resource.AbstractResourceManager.create(AbstractResourceManager.java:92)
	at org.eclipse.jface.resource.LazyResourceManager.create(LazyResourceManager.java:95)
	at org.eclipse.jface.resource.ResourceManager.createImageWithDefault(ResourceManager.java:192)
	at org.eclipse.jface.resource.ImageRegistry.get(ImageRegistry.java:208)
	at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.getImageFromURI(SWTPartRenderer.java:231)
	at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.getImage(SWTPartRenderer.java:241)
	at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.changePartTabImage(StackRenderer.java:670)
	at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.updateTab(StackRenderer.java:652)
	at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.subscribeTopicUILabelChanged(StackRenderer.java:410)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
	at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:183)
	at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:133)
	at org.eclipse.swt.widgets.Display.syncExec(Display.java:4853)
	at org.eclipse.e4.ui.workbench.swt.DisplayUISynchronize.syncExec(DisplayUISynchronize.java:34)
	at org.eclipse.e4.ui.internal.di.UIEventObjectSupplier$UIEventHandler.handleEvent(UIEventObjectSupplier.java:64)
	at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:206)
	at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:201)
	at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:151)
	at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:131)
	at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:73)
	at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:44)
	at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:55)
	at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:60)
	at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:424)
	at org.eclipse.e4.ui.model.application.ui.basic.impl.PartImpl.setIconURI(PartImpl.java:548)
	at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:107)
	at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:365)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
	at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:977)
	at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:939)
	at org.eclipse.e4.core.internal.di.InjectorImpl.internalInject(InjectorImpl.java:139)
	at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:386)
	at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:312)
	at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:203)
	at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:90)
	at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:59)
	at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:42)
	at org.eclipse.ui.internal.WorkbenchContributionFactory.create(WorkbenchContributionFactory.java:46)
	at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:134)

probably because something in the platform got downgraded and things does not match together anymore ...

I tried updating the whole setup to 2025-09 and there i don't see this problem even though the same version of these "problematic" plugins combination exist there:

but everything seems to work thus far, also without the negative dependency for apache http client....

I will test this further, but so far the issues seems to be resolved for me.

Thanks again Ed for your great help!

Bye Peter

[phermsdorf]

Bonus Question regarding the Eclipse version update:

i have a base configuration setup:Configuration file which is referenced from the actual setup which is a setup:Project.

For the update i changed the following in the base configuration:

But no update is proposed on already provisioned installations on startup. Is there anything else needed?

Thanks, Bye Peter

[merks]

Think of a Configuration as a bit like a macro. The contents are copied; the installation into the target installation.setup and the workspace into the target workspace.setup.

Nothing will reference the configuration and nothing you change in it will affect anything except the next installer on which you drop it.

Note that products generally only specify lower bounds on the things to install, so simply making https://download.eclipse.org/releases/2025-09/ available as an update site in any p2 task should result in an update.

Most configurations use a "latest" product version because they're intended to follow the development stream; there's generally also a latest-release for a more stable but still moving targets.

[phermsdorf]

Thanks @merks for the clarification!