-
Notifications
You must be signed in to change notification settings - Fork 10
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
Eliminate Buildscript by publishing to gradlePluginPortal #340
Comments
I suggest moving the contents of grails-web into the grails-core gradle plugin and simplifying some of the structure. A lot of plugins were split instead of just using config to enable/disable available tasks a plugin provides |
@davydotcom sure, it makes sense to merge grails-web and grails-core. Perhaps The hope is in the future I will get around to making grails-gsp independent of grails |
@davydotcom isn't a simple solution to just merge grails-web into grails-gradle-plugin then make org.grails.grails-plugin and org.grails.grails-gsp subprojects and just publish them? Later the other plugins could be make subprojects as well with a common core if needed |
actually, we can just publish grails-gradle-plugin and move org.grails.grails-gsp into the grails-gsp project |
somewhat related to #351 |
Related: #54 |
Somewhat related to #350 |
if
grails-gradle-plugin
is published to gradlePluginPortal,buildSrc/build.gradle
settings.gradle
and a
buildscript { }
are no longer needed for Grails Apps.
Also remove need for
grails-gradle-plugin currently consists of
org.grails.grails-web
should automatically be applied iforg.grails:grails-web-url-mappings
is presentorg.grails.grails-gsp
should automatically be applied iforg.grails:grails-gsp
is presentThe text was updated successfully, but these errors were encountered: