I have a requirement to be able to configure individual plugins (via property files packaged as part of the plugins) as part of a deployment-specific configuration. For example, say Plugin A as a.properties and once the application is installed, I would like to be able to configure properties by allowing a user to edit a.properties. If the plugin is packaged as a complete jar, then the user has problems getting to a.properties (since it is inside the jar). Old versions of eclipse ( < 3.1) exported plugins for Eclipse products as directories with a plugin.xml and code jar in.

How do I get the same behaviour in Eclipse 3.1?