Carrot2

I know what the problem is – we instantiate classes using reflection from plugins that have no direct relationship with the plugin these instantiated classes come from. This causes, as one side-effect, class not found exceptions for any class that is visible only from the target plugin. If this sounds vague that's because it is.

Anyway, I do have at least two different workarounds in my head
1) extract plugin JARs to separate plugins and re-export them,
2) add very specific buddy policy between sources/ algorithms and core/attribute plugins.

Will work on these.

Definitely the cause of our problems is the fact that we're using Java reflection to instantiate component instances. The extension (factory) model we previously had, in spite of the duplication it provided in addition to suite definitions, was more flexible and aligned well with the OSGi model. Extension implementations reside inside their defining plugin and since so have access to all of that plugin's resources (classes).

Let's stick to the suite definition model for now though. Consistency between the webapp, DCS and workbench is worth it.

Fixed in trunk.