-
Notifications
You must be signed in to change notification settings - Fork 11
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
Grails 6.2.2: Consolidate Gradle Plugin config to one location #408
Comments
@jamesfredley Are we ready to close this issue as not planned, as it was moved to the Grails 7 board? |
@matrei I've been thinking about this one more and I really think we should push this into Grails 6.2.2 It's a very simple change and we are only talking about modifying forge The reason for this change is that it seems that most Grails users are on 5.x or less. If we are not going to support 5.x and force them to upgrade to 6.x prior to the release of 7.x, it is going to upset a lot of people and make the 7.x upgrade more difficult for them. |
This is a very simple task. All that needs to be done is delete buildscript {
repositories {
maven { url "https://repo.grails.org/grails/core/" }
}
dependencies {
classpath "org.grails:grails-gradle-plugin:6.2.1"
}
}
plugins {
id "groovy"
id "com.github.erdi.webdriver-binaries" version "3.2"
id "war"
id "idea"
id "com.bertramlabs.asset-pipeline" version "4.5.1"
id "application"
id "eclipse"
}
apply plugin:"org.grails.grails-web"
apply plugin:"org.grails.grails-gsp" |
Is there any reason to go through 6 to get to 7? |
@jamesfredley said on Thursday he would get it done this week and then we can release 6.2.2 The reason to get it done in 6 is for anyone that upgrades to 6 before 7 is released. |
I am going to try to have a PR ready by the end of today and then we can continue the conversation against those code changes. |
Currently in 3 locations,
buildSrc/build.gradle
,settings.gradle
andbuild.gradle
.The text was updated successfully, but these errors were encountered: