exclude unnecessary files from jar artifact

[davidkron]

When we upgraded some of our applications to Grails 4.x we had some problems with the loading of views and layouts, which we had to debug and managed to track back to this plugin. The reason was that the views (notFound.gsp, main.gsp) contained in the distribution of this plugin were discovered before those in our own plugins. We managed to work around it by defining def loadAfter = ['cache'] in our own plugins.

Nevertheless, I think this plugin should not include stuff that is not needed by or does even break the consuming application. To address this, I made the following changes:

• remove asset-pipeline from the gradle build as the plugin doesn't provide any assets itself and therefore no unnecessary files are generated by the asset-pipeline gradle plugin
• remove grails-gsp from the gradle build to prevent the compiled GSPs from being added to the artifact (they are only used for demo and testing purposes when the plugin is run locally)
• remove pluginExcludes from the CacheGrailsPlugin class as this is not working anymore since Grails 3.x I think
• exclude demo content from the generated artifact using gradle

[darxriggs]

Also see

• pluginExcludes not honoured grails-core#9416
• be6cefe

[darxriggs]

@ZacharyKlein Do you have some feedback on this?

[darxriggs]

LGTM

@puneetbehl Can you have a look at this please? Now that the default branch is 5.0.x should this pull request be retargeted?

When #123 fixes the Chrome driver version issue and has been merged, it might be a good idea to rebase this pull request on the target branch.

[darxriggs]

In addition to this pull request I am also preparing another one. It will clean up the dependencies of the plugin to not pull in non-required dependencies (see #102).

[darxriggs]

@davidkron Could you rebase on the 5.0.x branch and update the pull request to use it as target branch?

[davidkron]

@darxriggs done

[darxriggs]

@puneetbehl Could you have a look at this one please?