Separate location for 'authorised' plugins?

[Satch]

If I am going to use this framework for my own RCP application, do I always have to put the 'authorised' plugins in a separate location to the rest of the plugins, or can I keep them all in the eclipse/plugins directory as usual? If I have to put them in a separate location, it will surely make deployment impossible using the standard product export wizard?

[Neil Bartlett]

Currently, yes you do have to locate them separately from the rest of the plugins. Otherwise they will always be loaded before Eclipse-JAAS gets the chance to check whether the user is authorized or not.

It does not mean you cannot use the standard product export, you just have to do a two-stage export. Firstly export your "core" plugins using the product export wizard. Then use the "deployable plugins and fragments" wizard to export the authorization-controlled plugins.

I know this is less than ideal, but it is necessary because of the constraints of the platform. The situation is likely to change, as the Equinox project is currently looking at how to evolve the platform to offer better support.

Regards,
Neil