There's a bit of work required for getting this plugin to work with a RCP, as opposed to the IDE itself.
I've gone through the process and there were two problems I had to tackle.
The plugin references some editor Theme stuff which is not available to a RCP application, only to the IDE.
The plugin uses Reflection and attempts to find some classes that normally will not be available in an RCP application. It faults with stacktraces in those cases.
To make the plugin useful for both use cases it must degrade gracefully when it is attempting to access IDE stuff. Of course there are also RCP application that include the Editor but such applications are probably the exception.
How to verify:
Let your NetBeans IDE build a skelletton NetBeans Platform Application (Maven-based of course).
Add nb-darcula as a dependency on the "app" project within that newly created multi-module project.
There will be some build-time as well as some run-time issues to solve. :-)
There's a bit of work required for getting this plugin to work with a RCP, as opposed to the IDE itself.
I've gone through the process and there were two problems I had to tackle.
To make the plugin useful for both use cases it must degrade gracefully when it is attempting to access IDE stuff. Of course there are also RCP application that include the Editor but such applications are probably the exception.
How to verify:
There will be some build-time as well as some run-time issues to solve. :-)