You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
that later causes this gradle bug: gradle/gradle#17236 when I build my grails project.
If I simply run "grails war" or "grails run", it will use 7.2, but if I delete gradle folder, it surprisingly creates .gradle\buildOutputCleanup\cache.properties with
gradle.version=6.9
This version I like more, because it doesn't cause that gradle bug, and my project builds just fine. I don't care what's the correct one, but both ways I expect grails to use exactly same version of gradle. Please correct me if I'm wrong.
Steps To Reproduce
No response
Environment Information
OpenJDK 1.8
Example Application
No response
Version
5.3.3 and 5.3.2
The text was updated successfully, but these errors were encountered:
The Grails Core and Grails Gradle Plugin use a different Gradle version to build the project. And, the Grails application ships with Gradle 7. They don't need to be using the same Gradle version across all the projects.
We suggest using the relevant Gradle commands instead of ./grailsw. As we move forward with Grails 6, duplicate commands have been eliminated, and it is preferable to rely on Gradle commands for your tasks.
Expected Behavior
Hi,
The version of gradle is expected to be the same for "create-app" and other commands, like "war", "run", but it's not always so.
I'm not sure where to find the proper gradle version number for those commands, for example, for Grails 5.3.3 it is listed as 6.9.4 at https://github.com/grails/grails-core/blob/v5.3.3/gradle/wrapper/gradle-wrapper.properties and 6.9.3 at https://github.com/grails/grails-gradle-plugin/blob/5.3.x/gradle/wrapper/gradle-wrapper.properties
Actual Behaviour
The problem is that inconsistent gradle versions may cause unexpected gradle behavior, here is an example:
For grails 5.3.3 (and same for 5.3.2), the "grails create-app" spawns gradle\wrapper\gradle-wrapper.properties with
that later causes this gradle bug: gradle/gradle#17236 when I build my grails project.
If I simply run "grails war" or "grails run", it will use 7.2, but if I delete gradle folder, it surprisingly creates .gradle\buildOutputCleanup\cache.properties with
This version I like more, because it doesn't cause that gradle bug, and my project builds just fine. I don't care what's the correct one, but both ways I expect grails to use exactly same version of gradle. Please correct me if I'm wrong.
Steps To Reproduce
No response
Environment Information
OpenJDK 1.8
Example Application
No response
Version
5.3.3 and 5.3.2
The text was updated successfully, but these errors were encountered: