| Update manager & version conflicts [message #435765] |
Tue, 23 August 2005 11:54  |
Eclipse User |
|
|
|
Originally posted by: dinne.bluemelon.org
Dear groupmembers,
We have developed a small RCP application which consists of:
1. a plugin consisting of a view and some preference pages
2. a win32 fragment containing dynamic link libraries (dll)
3. a RCP plugin
These plugins are wrapped in a feature which has been posted on an update
site. When modifications are made to the code we increase all the version
numbers of the plugins/features and repost the update site.
When the user starts his rcp application the update manager correctly
finds out that new updates are available. The user can install the updates
and the rcp application restarts.
The problem: The updated application does not behave correctly. After
examining the feature/plugin details in the 'about' dialog it is clear
that the old plugins/features are still available. Although this seems to
be normal behaviour the RCP application is clearly using the wrong (old)
plugins/features. When I manually delete the old plugins/features from the
eclipse directory everything is working fine.
What should be done to avoid these version 'conflicts'?
Yours sincerely,
Dinne Bosman
|
|
|
|
| Re: Update manager & version conflicts [message #435847 is a reply to message #435781] |
Wed, 24 August 2005 20:34  |
| Eclipse User |
|
|
|
Originally posted by: dinne.bluemelon.org
Thanks for pointing out the direction of a solution.
Can you be more specific how the RCP can automatically configure the
correct features/plugins?
After searching the fora I believe I have to do 'something' with the
org.update.configurator. If lets say in the features directory I have two
features
featureXYZ-1.0.0
featureXYZ-1.0.1
How can I change the behaviour of the configurator in such a way that it
will only install the feature/plugins with the highest version number?
Yours sincerely,
Dinne Bosman
|
|
|
| Re: Update manager & version conflicts [message #435856 is a reply to message #435847] |
Thu, 25 August 2005 09:09 |
| Eclipse User |
|
|
|
Originally posted by: dinne.bluemelon.org
Today I again tried to get the update manager to correctly update my
application. I now have a better idea what is going wrong:
I have two features
org.bluemelon.flexFeature (1.0.7) "Flex Plugin"
org.bluemelon.flexRCPFeature (1.0.7) "Flex P2000"
Several plugins:
org.bluemelon.flex (1.0.5) "Flex Plugin"
org.bluemelon.flexRCP (1.0.5) "Flex P2000"
And fragments:
org.bluemelon.flex.win32.win32.x86 (1.0.5) "Flex Plugin win32"
containing a JNI library (dll)
org.bluemelon.flexRCP.nl1 (3.1.6) "org.bluemelon.flexRCP.nl1.name"
After the update the configuration log tells me that:
org.bluemelon.flex (1.0.3) "Flex Plugin" [Installed]
org.bluemelon.flex (1.0.4) "Flex Plugin" [Installed]
org.bluemelon.flex (1.0.5) "Flex Plugin" [Active]
org.bluemelon.flex.win32.win32.x86 (1.0.4) "Flex Plugin win32" [Resolved]
org.bluemelon.flex.win32.win32.x86 (1.0.5) "Flex Plugin win32" [Resolved]
org.bluemelon.flexRCP (1.0.3) "Flex P2000 berichten ontvanger" [Installed]
org.bluemelon.flexRCP (1.0.4) "Flex P2000 berichten ontvanger" [Installed]
org.bluemelon.flexRCP (1.0.5) "Flex P2000 berichten ontvanger" [Active]
org.bluemelon.flexRCP.nl1 (3.1.5) "org.bluemelon.flexRCP.nl1.name"
[Resolved]
org.bluemelon.flexRCP.nl1 (3.1.6) "org.bluemelon.flexRCP.nl1.name"
[Resolved]
The correct plugins seem to be active. But older ones are installed as
well, this is probably not the problem.
The problem lies with the fragments, if I understand correctly fragments
are merged with their host plugin, so if there are two fragments
containing the same file as in this case
org.bluemelon.flex.win32.win32.x86 (1.0.4) "Flex Plugin win32"
org.bluemelon.flex.win32.win32.x86 (1.0.5) "Flex Plugin win32"
both contain a file named JLib.dll. How can I control that only version
1.0.5. has to be merged with the host plugin?
Yours sincerely,
Dinne Bosman
|
|
|
|
Powered by
FUDForum. Page generated in 0.24853 seconds
] 
Search
Help
Register
Login
Home
