Closed irstevenson closed 6 years ago
Copying the file 'build/classes/main/META-INF/grails-plugin.xml' manually to 'build/classes/java/main/META-INF/grails-plugin.xml' makes the build work again.
The culprit is here:
Adding this line to build.gradle fixes this issue:
sourceSets.main.output.classesDir = 'build/classes/groovy/main'
However classesDir is deprecated see https://docs.gradle.org/current/dsl/org.gradle.api.tasks.SourceSetOutput.html#N191E3 so this solution will not work when gradle 5 comes out.
Hmmm, an interesting one. Because as mentioned over in PR #20 , even if you add the gradle wrapper to the project grails itself ignores it.
Plus I've seen some issues raised saying grails is having issues with gradle 5.0. So maybe it's a case of 'wait and see' for this code base, and maybe make a note in the README.md for building.
By the way you can use gradle directly.
./gradlew install
./grailsw install
These commands will install the plugin, the only difference is which gradle version is used.
Merged in #20 , so will close this off - as that's really all that can be done from this end.
Attempting to build/install on a Debian machine with gradle 4.5.1 installed (via sdkman) results in the following:
I've attempted all kinds of wierd things, including basics like:
But somehow it keeps finding I have 4.5.1 on my machine and so spawns a daemon for it and bang.
Now this is probably more of a grails concern, however it seems to only impact this project because of the publishing plugin. So is it a bug, not sure. Maybe just be wary.
I have another machine with gradle 3.5 on it where things work, so I'll have to continue on there tomorrow.