Make Spring Boot compatible with GVM #21
Comments
|
@marcoVermeulen It's already pretty much in that form (although we use "spring-boot-cli" for the name of this component). We have an internal debate going on about whether to use "bin" or "dist" as the classifier, but that seems irrelevant. What was the problem exactly? |
|
I thought that the inconsistency between the archive name and install directory would throw it, but it turned out to work fine. Thanks in any case. |
philwebb
pushed a commit
to philwebb/spring-boot
that referenced
this issue
May 31, 2024
Bumps [gradle/gradle-build-action](https://github.com/gradle/gradle-build-action) from 2.10.0 to 2.11.1. - [Release notes](https://github.com/gradle/gradle-build-action/releases) - [Commits](gradle/gradle-build-action@87a9a15...982da8e) --- updated-dependencies: - dependency-name: gradle/gradle-build-action dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> See spring-projectsgh-21
philwebb
pushed a commit
to philwebb/spring-boot
that referenced
this issue
May 31, 2024
* spring-projectsgh-21: Bump gradle/gradle-build-action from 2.10.0 to 2.11.1 Closes spring-projectsgh-21
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In order for Spring Boot to be added to GVM, the binary zip file needs to comply with certain conventions. All technology currently supported by GVM is delivered in a zip file named as follows:
${name}-${version}-${freeform}.zipFor spring boot, it would be
spring-boot-0.5.0.M1-bin.zip.Internally, it would contain a folder named
${name}-${version}as:spring-boot-0.5.0.M1.If these minor changes could be made in the zip distro, I can proceed in adding it to gvm.
The text was updated successfully, but these errors were encountered: