Error in launching Eclipse RCP Application when we migrate from 4.15 to 4.26.

[NikitaIsalkar]

We are migrating our RCP based application from Eclipse 4.15 (RCP 4.15) to 4.26 (RCP 4.26), for that we have built our target platform using p2 repository of Eclipse 4.26 (https://download.eclipse.org/eclipse/updates/4.26/R-4.26-202211231800/)

We are able to successfully launch the application on our local machine, since all the plugins are getting resolved and started whenever its required.

We are able to build our application, and trying to launch the same, but we are facing an issue while launching the application.
We used to launch the application with Eclipse 4.15 using below parameters in config.ini file.

osgi.bundles=org.eclipse.equinox.common@2:start,org.eclipse.equinox.registry@:start,org.eclipse.equinox.app@:start,org.eclipse.update.configurator@3:start,org.eclipse.core.runtime@:start,org.eclipse.equinox.ds@:start,org.eclipse.equinox.event@:start,org.eclipse.equinox.util@:start,org.eclipse.e4.ui.workbench.addons.swt@:start

osgi.configuration.area=
osgi.instance.area=

 
eclipse.product=<product-pugin>

But when we use the same config file with Eclipse 4.26, we are getting below error, even though these plugins are present

org.osgi.framework.BundleException: Could not resolve module: org.eclipse.core.runtime [3]
Unresolved requirement: Require-Bundle: org.eclipse.core.jobs; bundle-version="[3.13.0,4.0.0)"; visibility:="reexport"

After going through the documentation and p2 repo, we understood that org.eclipse.equinox.ds and org.eclipse.equinox.util has been removed from eclipse 4.26.
Can someone please suggest any alternative way to load all the plugins and resolve them at runtime while launching the application.

Tested under this environment:

• Eclipse IDE/Platform version (as shown in Help > About): Eclipse 2022-12 4.26
• Using Java 17
• Migrating from Eclipse IDE/Platform version : Eclipse 2020-03 4.15

Community

• I understand reporting an issue to this OSS project does not mandate anyone to fix it. Other contributors may consider the issue, or not, at their own convenience. The most efficient way to get it fixed is that I fix it myself and contribute it back as a good quality patch to the project.

[merks]

It's always good to look at what's in the platform's own product:

https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/blob/bf07a20f62d06c1905d3027f3ad4ff561e573f90/eclipse.platform.releng.tychoeclipsebuilder/eclipse.platform.repository/sdk.product#L192-L200

The org.apache.felix.scr is particularly important; if I recall correct that was added when the *.ds thing was removed. In Oomph's Eclipse Installer product we just have these:

[NikitaIsalkar]

Hi @merks ,
Thank you for your response,

We did change our config.ini file to launch the application as below, but we are still not able to resolve the plugins, even though they are present.

config.ini
osgi.bundles=org.eclipse.equinox.simpleconfigurator@1\:start,org.apache.felix.scr@2\:start,org.eclipse.core.runtime@4\:start,org.eclipse.equinox.common@2\:start

Please find the below stack trace:

!ENTRY org.apache.felix.scr 4 0 2025-01-16 00:11:03.002
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.apache.felix.scr [2]
  Unresolved requirement: Import-Package: org.osgi.service.cm; version="[1.6.0,2.0.0)"; resolution:="optional"
  Unresolved requirement: Import-Package: org.osgi.service.metatype; version="[1.2.0,2.0.0)"; resolution:="optional"
  Unresolved requirement: Import-Package: org.apache.felix.service.command; version="[1.0.0,2.0.0)"; resolution:="optional"
  Unresolved requirement: Import-Package: org.osgi.service.component; version="[1.5.0,1.6.0)"
 
	at org.eclipse.osgi.container.Module.start(Module.java:463)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1852)
	at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1845)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1788)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1750)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1672)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)
 
!ENTRY org.eclipse.equinox.event 4 0 2025-01-16 00:11:03.033
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.equinox.event [6]
  Unresolved requirement: Import-Package: org.osgi.service.event; version="[1.3.0,1.5.0)"
 
	at org.eclipse.osgi.container.Module.start(Module.java:463)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1852)
	at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1845)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1788)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1750)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1672)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)

Also, when we use *.simpleConfigurator plugin, do we need to add ConfigUrl in config.ini (I am referring config.ini of eclipse->Configuration) file like below,

eclipse.product=org.eclipse.epp.package.jee.product
osgi.splashPath=platform\:/base/plugins/org.eclipse.epp.package.common
org.eclipse.equinox.simpleconfigurator.configUrl=file\:org.eclipse.equinox.simpleconfigurator/bundles.info
osgi.bundles.defaultStartLevel=4
eclipse.application=org.eclipse.ui.ide.workbench
osgi.instance.area.default=@user.home/workspace
osgi.bundles=reference\:file\:org.eclipse.equinox.simpleconfigurator_1.4.200.v20221111-1340.jar@1\:start
eclipse.p2.data.area=@config.dir/../p2
eclipse.p2.profile=epp.package.jee
osgi.framework=file\:plugins/org.eclipse.osgi_3.18.200.v20221116-1324.jar
osgi.framework.extensions=reference\:file\:org.eclipse.osgi.compatibility.state_1.2.800.v20221116-1440.jar
eclipse.buildId=4.26.0.20221201-1200

If yes, do we need to generate bundles.info on our own or eclipse will take care of it.

Please help!

[merks]

The errors Could not resolve module: org.apache.felix.scr [2] and Could not resolve module: org.eclipse.equinox.event [6] suggest that you have not included these in the launch/application.

I think I'm missing some context, i.e., how are you building this? Is the problem you describe happening for the product you built (with Tycho), or at development time in the IDE? If the latter, how you have specified what to include in the launch?

[NikitaIsalkar]

We are using ant build and InstallAnywhere to build the application, the build got successful, we get all the plugins inside the .exe file only. When we install the application, all the plugins are getting listed under one folder and they are getting resolved from there itself.

The problem is we are not able to resolve these plugins even though they are present at the desired location. We used the same build when we were working with Eclipse 4.15, and it always worked. But now after migration we are facing the issue.

[merks]

Are you saying the missing bundles it's complaining about are actually present in the plugins folder?

Ant build is pretty much on death row if not already basically dead so using Tycho would be highly recommended.

Try adding the missing things to one of your features and hope for the best that they will then properly included into the launched application that way.

[NikitaIsalkar]

Yes, we also tried using the config.ini file which is getting generated when we launch the application from Eclipse IDE itself, in this case, config.ini contains all the plugins under "osgi.bundles". We used this config file to launch our application, and it worked. It means when we provide all plugins list, they are getting resolved, but we want to give minimum plugins list which are responsible for the application startup.
As per my understanding, osgi itself loads required plugins if the launch is successful, correct me if I am wrong here.

Also, initially when we used eclipse 4.15, we used *.updateConfigurator to load the plugins, but now with 4.26 its not working.
Please see the config.ini which we used for 4.15

osgi.bundles=org.eclipse.equinox.common@2:start,org.eclipse.equinox.registry@:start,org.eclipse.equinox.app@:start,org.eclipse.update.configurator@3:start,org.eclipse.core.runtime@:start,org.eclipse.equinox.ds@:start,org.eclipse.equinox.event@:start,org.eclipse.equinox.util@:start,org.eclipse.e4.ui.workbench.addons.swt@:start

osgi.configuration.area=
osgi.instance.area=

 
eclipse.product=<product-pugin>

I am referring to the sdk.product for all the configurations and modified our config file as per the configurations provided, but still not able to resolve all the plugins.

[merks]

I think your time would be best invested in building with Tycho. I don't know exactly what you are doing and I don't know how to give advice for making an ant build work. I've suggested adding the missing things to a feature assuming a proper minimal product is produced by the tools you are currently using so I expect you simply need to include additional dependencies (in features) if those are missing at the end. I don't know what's in your target platform or how you are managing that nor how that affects your builds. I would personally throw that away the ant stuff because it will most likely stop working (maybe already has) and instead make a build work with Tycho. I know that may seem daunting and mysterious, but it will be effort well-invested in long term maintainability. I.e., how long should you repair your rusty old car before you decide it's better to buy a newer car that's in better shape.

In this folder, there is a very simple product definition:

https://github.com/eclipse-justj/justj.tools/tree/master/products/org.eclipse.justj.tools.sample.product

It does build:

https://ci.eclipse.org/justj/job/build-sample-product/

and that result does launch.

Copy and paste the pom.xml details to suit your product and application. All the examples you need are in the repository. You might even benefit from bundling a JRE with your application:

https://eclipse.dev/justj/?page=documentation

You don't need a fancy build machine, you can run the build locally:

What you have must be similar to that. That repo has a number of good simple examples of how to build bundles, features, products, and update sites all of which you can run locally. Pretty much everything you'd need to do in your case is there in a relatively simple form.

I'm going to close this because there is no bug here. It's always been possible to build products with every release. You can continue to ask questions here even if the issue is closed.