Updating the readme

[ctoestreich]

Giving some initial context to these plugins. Trying help untangle when to use certain gradle plugins and for what reason.

[bobbywarner]

👍

[graemerocher]

Only thing is the grails-gsp subproject is not a Gradle plugin, the gradle plugin is found in grails-gradle-plugin

[bobbywarner]

@graemerocher Yup, sorry. I'll update.

[bobbywarner]

Fixed here -- 535d4b5

[ctoestreich]

Ugh... see even I was confused about that. 🆘

[ctoestreich]

@graemerocher can you quickly explain the relationship between the grails-gradle-plugin and these projects such as grails-gsp and why the syntax says apply plugin: "org.grails.grails-web" Does the grails-gradle-plugin do something special with the this syntax?

[ctoestreich]

These appear more complicated than build scripts...

[hakanernam]

+1 about confused. Coming after "apply plugin war", one may be excused for thinking it is a gradle plugin.

[graemerocher]

So org.grails.grails-web is the id of the Gradle plugin. The Gradle plugins and their ids are defined here:

https://github.com/grails/grails-core/tree/master/grails-gradle-plugin/src/main/resources/META-INF/gradle-plugins

[graemerocher]

Whilst grails-web and grails-gsp contain the implementations for web related matters and GSP respectively.

Everything related to the Gradle plugin and the Gradle build is in https://github.com/grails/grails-core/tree/master/grails-gradle-plugin

[ctoestreich]

This all came about because we noticed that not applying the grails-gsp plugin would cause the project to not process the GSP and other web stuff (which we accidentally removed or used the wrong profile base). I think I may have incorrectly associated the project with the same name as being the actual gradle plugin.

Are the git projects named grails-web and grails-gsp included independently of their similarly named gradle plugins (which get wired up by the grails-gradle-plugin) or is there a directly relationship between these artifacts and the grails-gradle-plugin?

Having looked at some of the actual gradle plugins and the tasks they are exposing, classes they are using etc, it would appear that they simply share a name only and may only be indirectly related.

Sorry for making some cruft around this. I think what I ultimately want to create/need is a documentation that states what the grails gradle plugin applies actually do. This is specifically needed for when you start with a project or plugin using a profile that you decide to change the scope of and now need to add additional grails feature support

[graemerocher]

No problems. There is no direct relationship between the Gradle plugins and the grails-web and grails-gsp submodules (which are distinct things)

[ctoestreich]

Got it thanks.