Consider adding support for Grails

[matthurne]

No description provided.

[dougborg]

Hi @mhurne, thanks for the issue! Can you elaborate on this a bit? What would you want Grails support to look like / what is not working now that you think should?

[matthurne]

Sure - unless I'm missing something, "The problems with gradle and gradlew" described in the README also apply to grails and grailsw, perhaps with the exception of "You have to provide a relative path to build.Gradle".

[matthurne]

gw could mean "Gradle wrapper" and "Grails wrapper". I could imagine it determining whether it is being used in the context of a Gradle project or a Grails project and behaving accordingly. I could see one arguing that support for both under the same command would be a bad thing, though.

[dougborg]

Ah, I see what you mean, and I am somewhat open to this idea. I do think determining the appropriate context with one command may be the most difficult part and having a separate command for the grails wrapper would be a good place to start. gw is also meant to be a library - you can source it from other scripts, so we may be able to create a similar wrapper for grails and reuse some of the same functions.