Paul Webster Messages: 6859 Registered: July 2009 Location: Ottawa
Send to eclipse.technology.equinox.
Amit Mookerjee wrote:
> We are currently migrating our IDE product based on Eclipse 3.2 to
> Eclipse 3.6. In our Eclipse 3.2 based implementation we made extensive
> use of product extensions and referred to them via "*.link" files in the
> central "eclipse/links" folder.
> In eclipse 3.6 we see product extensions being supported with the
> recommended location for "*.link" files the "eclipse/dropins" folder.
> However we also see the following problem:
> When we refer to multiple product extension locations that contribute
> multiple versions of the same plugin the platform does not always pickup
> the latest plugin. Is this a bug in Eclipse 3.6?
> Also, we have seen that support for registering product extensions in
> the UI isn't available anymore. In eclipse 3.2 we had a UI for
> specifically adding an extension location using the following path
> "Help -> Software Updates -> Manage Configuration -> Add an Extension
> I believe the update manager has been completely redone and the new "p2"
> system is the standard mechanism for installing updates. However we have
> a large customer base which is using product extensions and I would like
> to know what type of support we can expect in eclipse 3.6 and later.
> Any guidance on product extensions in eclipse 3.6 will be much appreciated.
> Amit Mookerjee
The new system uses the SAT4J resolver to find a solution (plugins and
features that will work together). But the eclipse/dropins folder is a
"best effort" location, so installation can succeed without including
all of its contents.