Eclipse Community Forums: Plugin Development Environment (PDE) » Enforcing feature dependencies in Update site

Help

Home

Home » Eclipse Projects » Plugin Development Environment (PDE) » Enforcing feature dependencies in Update site

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

Enforcing feature dependencies in Update site [message #656032]

Wed, 23 February 2011 20:05

David

Messages: 4
Registered: February 2011

Junior Member

Hi all,

Hope someone can help me out with this update site question.

Some background: I have an update site which consists of one category. The category contains three features. One of the features is the "core" feature, the other two are optional extras. Both the optional extra features depend on the core feature being installed.

When the user browses my update site in Eclipse, the ideal behaviour would be that if the user selects one of the optional extra features, then the core feature should automatically be (force) selected.

Is this possible? Can I set a flag either the update site XML, or the feature.xml, to produce this behaviour?

If not, what's the best alternative? The underlying fundamental requirement is that the user cannot install an optional extra without also installing the core feature.

Thanks in advance!

Report message to a moderator

Re: Enforcing feature dependencies in Update site [message #656177 is a reply to message #656032]

Thu, 24 February 2011 13:12

Paul Webster

Messages: 6859
Registered: July 2009
Location: Ottawa

Senior Member

On 02/23/2011 03:05 PM, David wrote:
> Is this possible? Can I set a flag either the update site XML, or the
> feature.xml, to produce this behaviour?
> If not, what's the best alternative? The underlying fundamental
> requirement is that the user cannot install an optional extra without
> also installing the core feature.

If your optional features depends on the core feature, they won't
install successfully and the system will explain the missing feature to
users. If your optional features include the code feature, installing
one of them will install the core feature as well.

PW

--
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Platform_Expression_Framework
http://wiki.eclipse.org/Menu_Contributions
http://wiki.eclipse.org/Menus_Extension_Mapping
http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse .platform.doc.isv/guide/workbench.htm

Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions

Report message to a moderator

Re: Enforcing feature dependencies in Update site [message #656395 is a reply to message #656177]

Fri, 25 February 2011 12:38

Martin Skorsky

Messages: 112
Registered: July 2009

Senior Member

Use something similar to
<requires>
<import feature="core" version="1.1.0" match="compatible"/>
</requires>
in your feature.xml of the optional features. Now the installation of the optional feature installs also the core feature.

Report message to a moderator

Previous Topic:	Getting nullpointerexception while fetching current runtime project
Next Topic:	problem with a custom incremental builder

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 13:57:44 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter