Eclipse Community Forums: Rich Client Platform (RCP) » Why org.eclipse.equinox.simpleconfigurator/bundles.info can not be updated based on the plugins

Home » Eclipse Projects » Rich Client Platform (RCP) » Why org.eclipse.equinox.simpleconfigurator/bundles.info can not be updated based on the plugins

Show: Today's Messages :: Show Polls :: Message Navigator

Why org.eclipse.equinox.simpleconfigurator/bundles.info can not be updated based on the plugins [message #811344]

Fri, 02 March 2012 08:14

Hart H

Messages: 7
Registered: February 2012

Junior Member

Hi all,

I have a RCP project: when I copied the helpdoc plugin jar to the dir "plugins" and run this application, I found new installed plugin are not included in the file configuration/org.eclipse.equinox.simpleconfigurator/bundles.info. So I can not see this help doc in the help content area of our RCP.

If I copied the plugin jar to a Standard Eclipse, then one line info about this plugin will be added to the file configuration/org.eclipse.equinox.simpleconfigurator/bundles.info and the help content can be shown correctly.

Does anyone know when and how the project detect the plugins automatically?

This is my configuration/config.ini:
#This configuration file was written by: org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxFwConfigFileParser
#Tue Feb 21 14:11:59 GMT 2012
org.eclipse.update.reconcile=false
eclipse.p2.profile=profile
osgi.instance.area.default=@user.home/workspace
osgi.framework=file\:plugins/org.eclipse.osgi_3.6.2.R36x_v20110210.jar
equinox.use.ds=true
eclipse.product=myproject.product
osgi.splashPath=platform\:/base/plugins/myproject
osgi.framework.extensions=reference\:file\:org.eclipse.osgi.nl1_3.6.2.v201102251823.jar,reference\:file\:org.eclipse.osgi.nl2_3.6.2.v201102251823.jar,reference\:file\:org.eclipse.osgi.nlBidi_3.6.2.v201102251823.jar
osgi.bundles.defaultStartLevel=4
eclipse.p2.data.area=@config.dir/../p2
eclipse.application=myproject.application
osgi.bundles=org.eclipse.equinox.common@2:start,org.eclipse.update.configurator@3:start,org.eclipse.core.runtime@start,reference\:file\:org.eclipse.equinox.simpleconfigurator_1.0.200.v20100503.jar@1\:start
osgi.bundles.defaultStartLevel=4
org.eclipse.equinox.simpleconfigurator.configUrl=file\:org.eclipse.equinox.simpleconfigurator/bundles.info

Thanks,
Hart

Report message to a moderator

Re: Why org.eclipse.equinox.simpleconfigurator/bundles.info can not be updated based on the plugins [message #811520 is a reply to message #811344]

Fri, 02 March 2012 13:06

Brian de Alwis

Messages: 242
Registered: July 2009

Senior Member

The installation is now managed with a tool called p2; save yourself from grief and do *not* try to modify any of these files by hand!

If you want to add a single bundle, you can add it to the "dropins" folder. Providing you have the p2 dropins reconciler in your app, it will be picked up on restart.

Report message to a moderator

Re: Why org.eclipse.equinox.simpleconfigurator/bundles.info can not be updated based on the plugins [message #812647 is a reply to message #811520]

Sun, 04 March 2012 04:34

Hart H

Messages: 7
Registered: February 2012

Junior Member

Hi Brian,

Thanks for providing this help info.

Yes, I have added p2 function to my project, and can add a new plugin from the repository(remote site or local archive) in my RCP. But I can not import the help doc from local archive as RCP reports "No software site found in my plugins". The questions is I can add this jar file to a Standard Eclipse3.6.2 by putting this jar to plugin folder, but does not work in my RCP.
When I export the RCP, then I find the folder "p2" but can not find the folder "dropins" in the exported project. And when I add a folder "dropins" in my RCP manually and provide one plugin to my app, seems it will not be picked up on restart.
Did I miss some steps when exporting, so there is no dropins folder in my exported RCP. OR I missed some p2 plugins in my app? My plugins in feature.xml is as below:
org.eclipse.equinox.p2.artifact.repository
org.eclipse.equinox.p2.artifact.repository.nl1"
org.eclipse.equinox.p2.artifact.repository.nl2"
org.eclipse.equinox.p2.artifact.repository.nlBidi"
org.eclipse.equinox.p2.core"
org.eclipse.equinox.p2.core.nl1"
org.eclipse.equinox.p2.core.nl2"
org.eclipse.equinox.p2.core.nlBidi"
org.eclipse.equinox.p2.jarprocessor"
org.eclipse.equinox.p2.jarprocessor.nl1"
org.eclipse.equinox.p2.jarprocessor.nl2"
org.eclipse.equinox.p2.jarprocessor.nlBidi"
org.eclipse.equinox.p2.metadata"
org.eclipse.equinox.p2.metadata.generator"
org.eclipse.equinox.p2.metadata.generator.nl1"
org.eclipse.equinox.p2.metadata.generator.nl2"
org.eclipse.equinox.p2.metadata.generator.nlBidi"
org.eclipse.equinox.p2.metadata.nl1"
org.eclipse.equinox.p2.metadata.nl2"
org.eclipse.equinox.p2.metadata.nlBidi"
org.eclipse.equinox.p2.metadata.repository"
org.eclipse.equinox.p2.metadata.repository.nl1"
org.eclipse.equinox.p2.metadata.repository.nl2"
org.eclipse.equinox.p2.metadata.repository.nlBidi"
org.eclipse.equinox.p2.console.nl1"
org.eclipse.equinox.p2.console.nl2"
org.eclipse.equinox.p2.console.nlBidi"
org.eclipse.equinox.p2.director"
org.eclipse.equinox.p2.director.app"
org.eclipse.equinox.p2.director.app.nl1"
org.eclipse.equinox.p2.director.app.nl2"
org.eclipse.equinox.p2.director.app.nlBidi"
org.eclipse.equinox.p2.director.nl1"
org.eclipse.equinox.p2.director.nl2"
org.eclipse.equinox.p2.director.nlBidi"
org.eclipse.equinox.p2.directorywatcher"
org.eclipse.equinox.p2.directorywatcher.nl1"
org.eclipse.equinox.p2.directorywatcher.nl2"
org.eclipse.equinox.p2.directorywatcher.nlBidi"
org.eclipse.equinox.p2.engine"
org.eclipse.equinox.p2.engine.nl1"
org.eclipse.equinox.p2.engine.nl2"
org.eclipse.equinox.p2.engine.nlBidi"
org.eclipse.equinox.p2.extensionlocation"
org.eclipse.equinox.p2.extensionlocation.nl1"
org.eclipse.equinox.p2.extensionlocation.nl2"
org.eclipse.equinox.p2.extensionlocation.nlBidi"
org.eclipse.equinox.p2.garbagecollector"
org.eclipse.equinox.p2.garbagecollector.nl1"
org.eclipse.equinox.p2.garbagecollector.nl2"
org.eclipse.equinox.p2.garbagecollector.nlBidi"
org.eclipse.equinox.p2.reconciler.dropins"
org.eclipse.equinox.p2.reconciler.dropins.nl1"
org.eclipse.equinox.p2.reconciler.dropins.nl2"
org.eclipse.equinox.p2.reconciler.dropins.nlBidi"
org.eclipse.equinox.p2.touchpoint.eclipse"
org.eclipse.equinox.p2.touchpoint.eclipse.nl1"
org.eclipse.equinox.p2.touchpoint.eclipse.nl2"
org.eclipse.equinox.p2.touchpoint.eclipse.nlBidi"
org.eclipse.equinox.p2.touchpoint.natives"
org.eclipse.equinox.p2.touchpoint.natives.nl1"
org.eclipse.equinox.p2.touchpoint.natives.nl2"
org.eclipse.equinox.p2.touchpoint.natives.nlBidi"
org.eclipse.equinox.p2.ui"
org.eclipse.equinox.p2.ui.nl1"
org.eclipse.equinox.p2.ui.nl2"
org.eclipse.equinox.p2.ui.nlBidi"
org.eclipse.equinox.p2.ui.sdk"
org.eclipse.equinox.p2.ui.sdk.nl1"
org.eclipse.equinox.p2.ui.sdk.nl2"
org.eclipse.equinox.p2.ui.sdk.nlBidi"
org.eclipse.equinox.p2.updatechecker"
org.eclipse.equinox.p2.updatechecker.nl1"
org.eclipse.equinox.p2.updatechecker.nl2"
org.eclipse.equinox.p2.updatechecker.nlBidi"
org.eclipse.equinox.p2.updatesite"
org.eclipse.equinox.p2.updatesite.nl1"
org.eclipse.equinox.p2.updatesite.nl2"
org.eclipse.equinox.p2.updatesite.nlBidi"

Thank you very much!
Hart

Report message to a moderator

Re: Why org.eclipse.equinox.simpleconfigurator/bundles.info can not be updated based on the plugins [message #812652 is a reply to message #812647]

Sun, 04 March 2012 04:44

Hart H

Messages: 7
Registered: February 2012

Junior Member

Brian,

Do you have any good guide/article to introduce how to add P2 to my applications?

Thanks,
Hart

Report message to a moderator

Re: Why org.eclipse.equinox.simpleconfigurator/bundles.info can not be updated based on the plugins [message #813944 is a reply to message #812652]

Mon, 05 March 2012 21:48

Paul Webster

Messages: 6859
Registered: July 2009
Location: Ottawa

Senior Member

I'd start with http://wiki.eclipse.org/Equinox/p2/Adding_Self-Update_to_an_RCP_Application which must include p2 to use the update functionality.

PW

Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions

Report message to a moderator

Re: Why org.eclipse.equinox.simpleconfigurator/bundles.info can not be updated based on the plugins [message #814949 is a reply to message #813944]

Wed, 07 March 2012 03:23

Hart H

Messages: 7
Registered: February 2012

Junior Member

Thanks Paul.

Yes, I have configured as this guide before. And I can install a new plugin using the "Install new software".

My question here is whether a RCP using p2 still support to install a plugin by putting the jar file to dir Plugins of RCP directly? As the jar file can not be installed by "Install new software" as RCP reports "No software site found in this plugins". But this plugin can be shown in the earlier version of RCP which does not use P2 by putting it to the plugins folder directly.

Thank you very much!
Hart

Report message to a moderator

Re: Why org.eclipse.equinox.simpleconfigurator/bundles.info can not be updated based on the plugins [message #823903 is a reply to message #814949]

Mon, 19 March 2012 02:31

Hart H

Messages: 7
Registered: February 2012

Junior Member

Hi all,

Finally I found the root cause, I must start the p2 service to scan the plugins dir, the below snippet should be added to the .product file.
<configurations>
<plugin id="org.eclipse.core.runtime" autoStart="true" startLevel="4" />
<plugin id="org.eclipse.equinox.common" autoStart="true" startLevel="2" />
<plugin id="org.eclipse.equinox.ds" autoStart="true" startLevel="2" />
<plugin id="org.eclipse.equinox.p2.reconciler.dropins" autoStart="true" startLevel="5" />
<plugin id="org.eclipse.equinox.simpleconfigurator" autoStart="true" startLevel="1" />
</configurations>

Thanks.

Report message to a moderator

Previous Topic:	How to create an auto-extendable RCP product?
Next Topic:	Control based authorization in eclipse RCP

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 18 09:28:13 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter