+1, but with issues
Following Pauls variant: On 07.06.25 12:26, Paul King wrote: [...]
I checked: * "incubating" in distribution file names * NOTICE, LICENSE and DISCLAIMER files exist * No unexpected binary files in src zip * Verified signatures and checksums for all zips * Gradle bootstrap for src zip using: "gradle -p gradle-bootstrap" (I used gradle 8.11) * Build from source: "./gradlew build -PskipTests"
had it work till here and then I wanted to install. It is a bit strange to put a INSTALL file in there, but then to just tell people to go to a website, where the instruction for the latest build are linked... which my not be the current build? There it says to do "./gradlew install" which would not have worked at all without the bootstrap step, which is not mentioned there. The install finally wants to verify the grails distribution pgp key... why? I really do not want to push to public maven! Also not using :grails-async-core:signMavenPublication
Well... I take a look at the binary distribution... [...]
* I tried: ./grails-forge-cli-help ./grails-forge-cli create-app hello ./grails-forge-cli --version ./grails-shell-cli --version
those work... but the installation instruction even for the binary version are kind of useless to me. The apps those commands create depend on released (even if only locally) grails jars. But how do I "release" them if I have the binary version?
* I think additional guidance in the vote email on what to read to build from src would be useful for newbies
very much so. [...] bye Jochen
