| why eclipse load the old plugin [message #329041] |
Wed, 11 June 2008 01:34  |
Eclipse User |
|
|
|
Hi, all
I have two plug-ins with different version, they are: x.y.myPlugin(3.0.0)
and x.y.myPlugin(4.0.0).
The problem is that the older one (x.y.myPlugin(3.0.0)) is loaded after
eclipse started.
But I think that eclipse manages all the plug-in and their version as well,
and it should make sure that the newer plug-ins are always loaded.
Did I missing anything?
Thanks & Best Regards!
Nick
|
|
|
|
| Re: why eclipse load the old plugin [message #329078 is a reply to message #329047] |
Thu, 12 June 2008 03:44  |
| Eclipse User |
|
|
|
Thanks Ed,
I got it, and it works fine after I set "singleton:=true" for the
Bundle-SymbolicName of the newer plug-in x.y.myPlugin(4.0.0),
But what I wandered is that why eclipse active the old one if I did not set
"singleton:=true" though the two plug-ins are both resolved successfully?
--
Thanks & Best Regards!
Nick
"Ed Merks" <merks@ca.ibm.com> wrote in message
news:g2o2ur$37r$2@build.eclipse.org...
> Nick,
>
> Try running with -clean -debug and looking at the
> <workspace>/.metadata/.log. It should describe what plugins are being
> activated and the details of that will likely help explain. For example,
> the newer plugin might require things that aren't available or there
> might be other plugins that specifically require the older version of
> the plugin, since plugin dependencies can specify ranges...
>
>
> Nick Tan wrote:
>> Hi, all
>>
>> I have two plug-ins with different version, they are:
>> x.y.myPlugin(3.0.0) and x.y.myPlugin(4.0.0).
>> The problem is that the older one (x.y.myPlugin(3.0.0)) is loaded
>> after eclipse started.
>>
>> But I think that eclipse manages all the plug-in and their version as
>> well, and it should make sure that the newer plug-ins are always loaded.
>> Did I missing anything?
>>
>> Thanks & Best Regards!
>> Nick
|
|
|
Powered by
FUDForum. Page generated in 0.03417 seconds
Home