This repository has been archived by the owner on Jan 5, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 85
Custom generator does not run any more #1050
Comments
Am I right in the assumption that you used the "Configure for Plugin Export" option? We changed the extension point schema for registering a custom generator. Now it is required to provide a GeneratorModule under the "bindings" key. The plugin.xml that is generated for a custom generator project is indeed incomplete in this regard. For a workaround you can do the following:
This should solve the NPE and make the generator run again! |
tkutz
added a commit
that referenced
this issue
Oct 19, 2016
When creating new custom generator configured for plugin export, the extension point registration needs a 'bindings' setting which defines a module class that contains all generator specific Guice bindings.
tkutz
pushed a commit
that referenced
this issue
Oct 26, 2016
When creating new custom generator configured for plugin export, the extension point registration needs a 'bindings' setting which defines a module class that contains all generator specific Guice bindings.
Fixed with pull request #1057 |
We have just released an intermediate version 2.8.1, where this issue is fixed. |
OK. I've got the custom generator running again. Thank you. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After invoking the custom generator a dialog with a NullPointerException appears with no stack trace. The console show the following stack trace:
Even a new custom generator inside a fresh workspace setup using your documentation shows the same behavior.
The text was updated successfully, but these errors were encountered: