Better Plug in Development Experience

Acceptance Criteria

1. We don't want to have to follow instructions to set-up our IDE
2. We don't want to have to manually edit 'META-INF/service' files to create new plug-ins since it's hard to explain and has no error feedback (ideally we'd use annotations rather than 'META-INF/service' files in the first place)
3. We'd like a free build to create the plugin jar we distribute to others
4. We don't want to have to run the build or install a jar to test our plug-in
5. We'd like to be able to easilly debug our plug-in within the IDE
6. We'd like to be able to step through model code while developing our plug-ins
7. We'd like the opportunity to use spec test to create automated tests for our plug-in
8. We'd like it to be easy to fix any bugs we find in the model code and/or easilly update to the latest version of the model code
9. We'd like not to have to download the source code since developers may have an aversion to having to work with source or installing Git.
10. Projects must be able to use dependencies from other libraries.
11. The dependenices required for one plug-in must not conflict with the libraries for any other plug-in.
12. Allow use of development plug-in from the command without requiring the use of an IDE.
13. It would be preferable not to force Gradle on people.
14. It should be possible at some future point to create JavaScript plug-ins.

Proposal

To be defined...