Community
Participate
Working Groups
Eclipse lacks customization capabilities aimed at end users and product packagers. More generally, component development and use is fraught with producer/consumer problems. Component producers implement solutions that address a number of use-cases and scenarios but inevitably consumers come up with additional, sometimes quite divergent requirements. We will investigate mechanisms and facilities that allow component consumers to "override" or replace metadata specifications in the components they are consuming. Such mechanisms would, for example, allow consumers to configure menus, tool bars, and perspectives of their Eclipse installation as well as refine plug-in dependency declarations. [Runtime, UI]
FYI: http://wiki.eclipse.org/index.php/Product_Customization
I've started fleshing out a sketch of a generalized OSGi solution at the above-mentioned wiki page. Any input is welcome.
I'm looking at using the new transform mechanism to implement a security framework in an RCP application. So far things are working fine with the initial work you've done. The only thing I was surprised by (and I'm not an OSGi expert), is that I need to clear my configuration cache to get this to work. Otherwise, the plugin descriptors are not passed through the XSL transform. I'm wondering if this is just a fact of life because of the way OSGi loads resources, or if this something that could be fixed by future implementations of the transform mechanism? Thanks for your help.
If you're talking about plugin.xml transforms then yes, -clean is needed at the moment - the extension registry caches the result of parsing these files and as yet changes via transformation are not picked up. This may change once/if I get the caching story in the transformers fixed or it may need to be raised against equinox registry. I'm not sure yet.
I'd appreciate a couple of examples for using the transforms. Right now I only understand they exist... I'm building an RCP application that uses projects etc and therefore carries a lot of IDE baggage. It would be nice to show how working sets and other contributions could be disabled. Thanks!
(In reply to comment #5) > I'd appreciate a couple of examples for using the transforms. Right now I only > understand they exist... The above mentioned wiki contains examples of using XSLT transforms (although not specifically working sets). The link at the bottom, http://wiki.eclipse.org/Equinox_Transforms has instructions on running some equinox examples, including running the XSLT transforms. PW
Thanks for the hint Paul. Do you think the wiki or this bug could be enhanced with a description how to include this in an RCP app? Have not been able sofar adding the right plugins, e.g. equinox.transform is not available as plugin dependency? Sorry- not an OSGI wizard :( Thanks, Andreas
This plan item was deferred, and no further work is planned in the runtime area for this item. The Equinox transforms can be used to customize applications at the runtime and extension registry level. Bug 252650 is exploring model-based customization of the Eclipse UI, which captures many of the scenarios from this original plan item.
