My current hold up is the fact that the Activator.java file is created in PluginClassCodeGenerator which I have no access to. Therefore currently my Scala implementation ends up with the activator being created twice, once in scala and once in java.
Why does this come up twice... you have your own activator template? For example, we have templates for OSGi bundles like Hello OSGi Service that customize the activator and only end up with one activator.
I'm willing to submit a patch to fix the problem as long as the patch would fit into the future vision of the PDE. My proposed solution is:
1) Make an interface for PluginClassCodeGenerator
2) Allow users to specify a new PluginClassCodeGenerater on the IFieldData interface (or within another public API).
3) Default the PDE classes to using the existing implementation of the PluginClassCodeGenerator.
We love patches in PDE and would be willing to work with y'all. There's actually a desire to support plug-ins written in other languages within PDE. I would love to hook up and see what you guys are doing with Scala/PDE so we can see what PDE needs to open up in terms of APIs. PDE is having a bit of an evolution now as before it was meant to be just a tool and now it's becoming more of a platform so it should be fun :)
Let me know when you want to setup a time to chat. I idle in IRC all the time in #eclipse-dev as 'zx'
