Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » why eclipse load the old plugin
why eclipse load the old plugin [message #329041] Wed, 11 June 2008 05:34 Go to next message
nick tan is currently offline nick tanFriend
Messages: 56
Registered: July 2009
Member
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 #329047 is a reply to message #329041] Wed, 11 June 2008 08:40 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: merks.ca.ibm.com

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
Re: why eclipse load the old plugin [message #329078 is a reply to message #329047] Thu, 12 June 2008 07:44 Go to previous message
nick tan is currently offline nick tanFriend
Messages: 56
Registered: July 2009
Member
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
Previous Topic:Prevent plugin installation or warn users about JVM versions
Next Topic:delete action as object contribution ...
Goto Forum:
  


Current Time: Wed Jul 17 12:27:22 GMT 2024

Powered by FUDForum. Page generated in 0.03993 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top