PartMaster

Some days ago I received an e-mail related to Obfuscate4e and multi-plugin RCP projects. And as we just got an forum entry with the same topic I will publish the e-mails here.

Also, for RCPs built from multiple plugins, each plugin needs to have custombuildcallbacks.xml generated, yes? It's not as simple as just doing this of the main plugin with the product definition, is it?

Yes, that's true. Each plugin might be used in different contexts/products and contains it's own obfuscation config.

Furthermore the product might be extended by additional plugins and someone has to remind that each plugin also has to be added to the product's obfuscation config, if it was defined product wide. Even more, if a plugin exports an additional package, than it might be easier to update plugin configs then to update product configs.

Conclusion: I think it's a better approach to store the obfuscation config together with the plugin. The real overhead work has to be done just once during the obfuscate4e setup. And you gain an optimum(?) of flexibility afterwards.