-
Notifications
You must be signed in to change notification settings - Fork 949
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pluginExcludes not honoured #9416
Comments
They have to be defined in https://github.com/grails-plugins/grails-cache/blob/master/build.gradle#L80 |
That doesn't entirely work because the domain classes are still added to the META-INF/grails-plugin.xml file. The application then complains about those missing domain classes if it has the plugin installed. This should probably be documented in the migration guide too 😄 |
As I said you need to define both in |
So the form of the I think this should be left open as a documentation issue. |
I created a pull request for this. |
Thanks! |
It seems that Grails 3 doesn't honour the
packageExcludes
property when packaging plugins. To demonstrate, try building the Hibernate Filters plugin. It excludes the domain classes, but these are still packaged in the plugin JAR.There's no mention of
pluginExcludes
in the migration chapter of the user guide, so I assume it's still supposed to work. To be honest I'd prefer an approach that fits better with the Grails or Gradle model. It feels hacky. These classes should really be in the test source set.The text was updated successfully, but these errors were encountered: