Eclipse Community Forums: Eclipse Platform » optional plugin dependencies?

Help

Home

Home » Eclipse Projects » Eclipse Platform » optional plugin dependencies?

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

optional plugin dependencies? [message #152374]

Mon, 03 November 2003 14:03

Markus Gebhard

Messages: 20
Registered: July 2009

Junior Member

As far as I understand plugins only have access to classes that are on
the classpath created from the <runtime> and <requires> parts in the
plugin manifest (plugin.xml) and to the classes of the JRE of course. If
there is a plugin missing, that I have specified to be depending on, my
plugin is disabled.

Now I have a plugin that _optionally_ depends on another plugin. I.e:
When the other plugin is available, my plugin supports the complete set
of features by also using classes from the other plugin. When the other
plugin is not available, some buttons will be disabled, but the plugin
will still work.

Detecting the availability of the other plugins classes at runtime is no
problem, but is there a way to specify this optional depedency in the
plugin.xml?

Thanks,
Markus
--
http://www.jdemo.de - Demonstrating for better code

Report message to a moderator

Re: optional plugin dependencies? [message #152397 is a reply to message #152374]

Mon, 03 November 2003 14:34

Jerome Lanneluc

Messages: 572
Registered: July 2009

Senior Member

<requires>
<import plugin="another.plugin" optional="true"/>
</requires>

"Markus Gebhard" <markus@jave.de> wrote in message
news:bo5n45$aji$1@eclipse.org...
> As far as I understand plugins only have access to classes that are on
> the classpath created from the <runtime> and <requires> parts in the
> plugin manifest (plugin.xml) and to the classes of the JRE of course. If
> there is a plugin missing, that I have specified to be depending on, my
> plugin is disabled.
>
> Now I have a plugin that _optionally_ depends on another plugin. I.e:
> When the other plugin is available, my plugin supports the complete set
> of features by also using classes from the other plugin. When the other
> plugin is not available, some buttons will be disabled, but the plugin
> will still work.
>
> Detecting the availability of the other plugins classes at runtime is no
> problem, but is there a way to specify this optional depedency in the
> plugin.xml?
>
> Thanks,
> Markus
> --
> http://www.jdemo.de - Demonstrating for better code
>

Report message to a moderator

Re: optional plugin dependencies? [message #152481 is a reply to message #152397]

Mon, 03 November 2003 16:18

Markus Gebhard

Messages: 20
Registered: July 2009

Junior Member

Jerome Lanneluc wrote:

> <requires>
> <import plugin="another.plugin" optional="true"/>
> </requires>

Great! Thanks.
Markus

Report message to a moderator

Previous Topic:	Setting a Custom Browser for Help in OS X
Next Topic:	[ANNOUNCE] Spectrum Announces Integration between SpectrumSCM and the Eclipse platform

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Nov 07 12:13:15 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter