Deployed RCP jar in the RCP_EXTN_FOLDER. Built SOM and created a as per the installation guide and copied the contents of the new zip file that was created as part of the build to the .The build is working fine on the server and changes can be seen if client is launched directly from the server. Now when the client is launched from a remote system which is connected to the server it shows the pop up ˜ A new update has been detected. Restart application for the update to take effective˜.
When the application is restarted other changes get updated but the config.ini file is not getting updated and it is not having the latest jar names. In updatets.xml at the server end, the time for config.ini is not getting updated while the time changes for the other files. Due to which this file does not get updated at the remote client.
config.ini should get updated to reflect the latest change
config.ini was intentionally left out to prevent certain update related issues.
Resolving the problem
Currently we maintain the list of plugins in osgi.bundle property in
config.ini. In Eclipse 3.3 and earlier, there was an update configurator
(org.eclipse.update.configurator). It was installed on the osgi.bundles
list . It would scan the plugins directory and automatically install
everything it found there. This configurator is present in our current
config.ini . But the plugin jar wasnt present in the plugins folder. So,
the following changes are required to make this work:
1. Edit config.ini so that it has following entry for osgi.bundles property
2. Download the eclipse-platform-3.3-win32.zip from
org.eclipse.update.configurator_3.2.100.v20070615 jar is present in plugins
folder of the eclipse.
3. Copy the org.eclipse.update.configurator plugin obtained in step#2 to
plugin directory of the rcp client.
4. Now, rebuild the com/som client
5. Distribute this new client to all remote location.
After this update configurator will automatically pick up all the plugins
present in the plugins directory.
Note: After making these changes, the plugins introduced would be picked up automatically but config.ini would not get updated.