Eclipse Community Forums: P2 » Eclipse can't load all bundles after upgraded to eclipse 4.10

Home » Eclipse Projects » P2 » Eclipse can't load all bundles after upgraded to eclipse 4.10

Eclipse can't load all bundles after upgraded to eclipse 4.10 [message #1800936]

Wed, 09 January 2019 21:46

Eclipse User

After I upgraded the target platform of my product from eclipse4.3 to eclipse4.10, my product can't load all bundles in the plugins folder by default anymore, could you please tell me how to configure eclipse4.10 to load all bundles in the plugins folder by default except using org.eclipse.equinox.simpleconfigurator and bundles.info ?

When using eclipse4.3 as target platform, I can configure eclipse to load all bundles by default through configuring the following codes in config.ini:

osgi.bundles=org.eclipse.equinox.common@2:start,org.eclipse.update.configurator@3:start,org.eclipse.equinox.ds@2:start,org.eclipse.core.runtime@start

but after I upgraded my target platform to eclipse4.10, it doesn't work anymore.

Thanks in advance,
Chao

[Updated on: Wed, 09 January 2019 23:02] by Moderator

Re: Eclipse can't load all bundles after upgraded to eclipse 4.10 [message #1800939 is a reply to message #1800936]

Wed, 09 January 2019 22:54

Eclipse User

I know we had to change this in Oomph's product definition because org.eclipse.equinox.ds has been removed from the platform's feature(s):

      <plugin id="org.apache.felix.scr" autoStart="true" startLevel="2" />

I.e., believe org.apache.felix.scr is the placement for org.eclipse.equinox.ds for starting the services early.

Re: Eclipse can't load all bundles after upgraded to eclipse 4.10 [message #1800941 is a reply to message #1800939]

Thu, 10 January 2019 01:40

Eclipse User

Thanks for your reply Ed,

My RCP doesn't use Oomph, so I tried to replace the org.eclipse.equinox.ds with org.apache.felix.scr in osgi.bundles attribute, but it still launch failed.

BR
Chao

[Updated on: Thu, 10 January 2019 02:32] by Moderator

Re: Eclipse can't load all bundles after upgraded to eclipse 4.10 [message #1800960 is a reply to message #1800941]

Thu, 10 January 2019 06:14

Eclipse User

Is org.eclipse.equinox.simpleconfigurator / bundles.info the only way to control to load bundles?
(Except writing all bundles into the osgi.bundles attribute)

[Updated on: Thu, 10 January 2019 06:17] by Moderator

Re: Eclipse can't load all bundles after upgraded to eclipse 4.10 [message #1800976 is a reply to message #1800960]

Thu, 10 January 2019 09:25

Eclipse User

Generally OSGi only loads bundles that were explicitly specified (i.e., in the osgi.bundles property or via other means like the simpleconfigurator). The update.configurator was a bit of a hack and caused other bad behaviour such as updated or removed bundles being reloaded. The update.configurator behaviour was gutted due to bug 527783.

How are you building and assembling your app?

Re: Eclipse can't load all bundles after upgraded to eclipse 4.10 [message #1801010 is a reply to message #1800976]

Thu, 10 January 2019 22:31

Eclipse User

Thank you very much!

I am not very sure what do you mean about "How are you building and assembling your app?", before we used a customized config.ini and configured it to load all bundles in the plugins folder.
We'll change our system to generate the bundles.info.

BR
Chao

Re: Eclipse can't load all bundles after upgraded to eclipse 4.10 [message #1801044 is a reply to message #1801010]

Fri, 11 January 2019 10:53

Eclipse User

I meant are you using Maven/Tycho, or PDE Build, or some other technology?

You could also consider using the org.eclipse.equinox.p2.reconciler.dropins bundle, which is like the org.eclipse.update.configurator but installs all bundles found in the dropins/ folder.

Re: Eclipse can't load all bundles after upgraded to eclipse 4.10 [message #1801105 is a reply to message #1801044]

Sun, 13 January 2019 22:15

Eclipse User

Yes, we are using Maven/Tycho; I'll check the org.eclipse.equinox.p2.reconciler.dropins bundle.

Thank you!
Chao

Re: Eclipse can't load all bundles after upgraded to eclipse 4.10 [message #1801159 is a reply to message #1801105]

Mon, 14 January 2019 12:31

Eclipse User

Just ran into this problem. See https://github.com/archimatetool/archi/issues/429

Our RCP app uses a custom method of adding plugins to the "plugins" folder and doesn't use P2 for this. Therefore using the simpleconfigurator is not an option.

How easy/hard would it be to use org.eclipse.equinox.p2.reconciler.dropins and the dropins folder? Does our RCP app need to do anything special?

Re: Eclipse can't load all bundles after upgraded to eclipse 4.10 [message #1801166 is a reply to message #1801159]

Mon, 14 January 2019 13:42

Eclipse User

See the p2 Getting Started guide for details on dropins:

https://wiki.eclipse.org/Equinox/p2/Getting_Started#Dropins

But the simple answers are: "easy" and "just include the bundle and mkdir dropins/" :-)

Do realize though that officially the dropins is deprecated and not recommended. And be sure to read the section in the Getting Started guide on debugging dropins.

Brian.

Re: Eclipse can't load all bundles after upgraded to eclipse 4.10 [message #1809397 is a reply to message #1801166]

Mon, 15 July 2019 09:05

Eclipse User

Is there a way to force upsate/simple configurator to retake bundles from plugins folder?

we are creating RCP application with a maven, and actually time to time we need to patch existing application with new bundle version, but it is now ignored.

Is there a way to instruct any configurator to take new version of bundle?

Thanks

Re: Eclipse can't load all bundles after upgraded to eclipse 4.10 [message #1809468 is a reply to message #1809397]

Tue, 16 July 2019 10:00

Eclipse User

The recommended way is to use p2 to download and apply changes. You can use p2 programmatically through its API. The p2 FAQ has some pointers.

Re: Eclipse can't load all bundles after upgraded to eclipse 4.10 [message #1809504 is a reply to message #1801166]

Wed, 17 July 2019 02:34

Eclipse User

Hi,

I have looked into that, but as the build features contains exact version of bundles, and If I try to use provinstall with newer version of bundle, it give me error that dependency to old version can not be satisfied, so product could not beresolved.

Actually we are building about 100+ bundles, so it make no sense to install newer feature as it would update much more bundles than the only one, and we have requirement to allow really small patches.

Or is there a way to generate bundle.info property without versions? I remember that with PDE it was possible, but with tycho I didn't found a way to do it.

Thanks in advance.

Re: Eclipse can't load all bundles after upgraded to eclipse 4.10 [message #1809808 is a reply to message #1809504]

Tue, 23 July 2019 14:30

Eclipse User

Take a look at feature patches.

Re: Eclipse can't load all bundles after upgraded to eclipse 4.10 [message #1811303 is a reply to message #1809808]

Fri, 30 August 2019 06:28

Eclipse User

Hi again,
Thanks for feature patches. They do exactly what I wanted, but unfortunately it is only one time patch.

I have also tryied to uninstall that patch later and It fails as it could not find original version of patched bundle - which is located in plugins folder.

I think problem is that when tycho materialize product, it keeps original sites there (local folders on build machine), and p2 does not have those folders available when uninstalling feature patch.

Is there a way to inform p2 to check plugins/features folders for existing bundles?

Re: Eclipse can't load all bundles after upgraded to eclipse 4.10 [message #1811309 is a reply to message #1811303]

Fri, 30 August 2019 08:54

Eclipse User

Just find out that you can install new version of patch when you directly uninstall older version in that step - there is not problem with missing plugins as you will replace them directly.

Re: Eclipse can't load all bundles after upgraded to eclipse 4.10 [message #1811323 is a reply to message #1811309]

Fri, 30 August 2019 15:58

Eclipse User

There I another alternative: the dropins/ folder. It's officially deprecated though still available, and not recommended for a variety of reasons, especially when you have hundreds of bundles -- managing conflicts can be hairy and you may end up with untested combinations. Whereas features let you manage a set of tested combinations.

Previous Topic:	How to get correct version jre number generated in eclipse.ini
Next Topic:	Good place for hosting p2 repositories

Goto Forum:

-=] Back to Top [=-

Current Time: Mon Jun 23 12:56:35 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter