Search Criteria
Package Details: micronaut 1.3.5-1
Git Clone URL: | https://aur.archlinux.org/micronaut.git (read-only, click to copy) |
---|---|
Package Base: | micronaut |
Description: | Application Framework |
Upstream URL: | https://github.com/micronaut-projects/micronaut-core |
Licenses: | Apache |
Submitter: | Svenstaro |
Maintainer: | None |
Last Packager: | kvbx |
Votes: | 2 |
Popularity: | 0.000000 |
First Submitted: | 2019-06-21 09:01 (UTC) |
Last Updated: | 2020-05-25 09:50 (UTC) |
Dependencies (1)
- java-environment (java-gcj-compat, zulu-10-bin, jdk12-openj9-bin, zulu-12-bin, jdk12, jdk13-openj9-bin, jdk9-openj9-bin, jdk10, jdk10-openj9-bin, jdk14-openj9-bin, jdk7, zulu-14-bin, amazon-corretto-15, zulu-embedded-jdk8, sapmachine-jdk-bin, amazon-corretto-16, jdk8-graalvm-bin, jdk16-graalvm-bin, jdk8-openjdk-shenandoah, zulu-16-bin, jdk16-adoptopenjdk, jdk16-microsoft-openjdk, jdk11-msopenjdk-bin, jdk18-beta-temurin, jdk8-arm, jdk17-jetbrains, liberica-jdk-11-bin, liberica-jdk-11-lite-bin, liberica-jre-11-bin, jdk11-jetbrains-imfix, java-openjdk-loom-ea-bin, jdk7-j9-bin, jdk7r1-j9-bin, jdk8-j9-bin, jdk11-j9-bin, jdk11-jbr-xdg, jdk16-openjdk, jdk13-openjdk, jdk14-openjdk, jdk-bcl, amazon-corretto-18, zulu-18-bin, zulu-13-bin, bishengjdk-17, jdk-arm, jdk11-openj9-bin, jdk-openj9-bin, jdk-jbr-xdg, jdk18-openjdk, jdk18-openj9-bin, jdk-android-studio, amazon-corretto-19-bin, zulu-19-bin, jdk19-graalvm-bin, liberica-jre-11-full-bin, jdk19-graalvm-ee-bin, jdk13-openjdk-bin, zulu-embedded-jdk, jabba-bin, jdk8-openjdk-xdg, jdk17-openjdk-xdg, jdk15-openjdk, zulu-embedded-jdk11, liberica-jre-8-full-bin, jdk11-graalvm-bin, jdk18-temurin, jdk19-openjdk, jdk11-microsoft-openjdk, jdk-openj9, jdk11-graalvm-ee-bin, jdk17-jetbrains-imfix, jdk11-openjdk-dcevm, jdk12-openjdk, jdk8-dragonwell-extended, jdk-jetbrains, jdk8-dragonwell-extended-bin, jdk8-dragonwell-standard-bin, jdk11-dragonwell-extended-bin, jdk11-dragonwell-standard-bin, jdk11-jetbrains-bin, jdk8-openj9-bin, jdk17-dragonwell-standard-bin, amazon-corretto-8, zulu-8-bin, zulu-20-bin, zulu-jdk-fx-bin, jdk-temurin, jdk17-graalvm-ee-bin, jdk20-graalvm-ee-bin, liberica-jdk-8-full-bin, jdk20-graalvm-bin, jdk17-graalvm-bin, mandrel-bin, jdk-lts, jdk17-zulu-prime-bin, jdk8-graalvm-ee-bin, jdk8-aarch64, jdk8-temurin, jdk8-adoptopenjdk, liberica-jdk-11-full-bin, liberica-jdk-17-full-bin, amazon-corretto-20-bin, amazon-corretto-17, zulu-15-bin, jdk8, jdk21-jetbrains-bin, jdk21-jetbrains-imfix, amazon-corretto-11, jdk17-jetbrains-bin, jdk-microsoft-openjdk, jdk17-openj9-bin, jdk20-openj9-bin, java-openjdk-bin, zulu-21-bin, amazon-corretto-21-bin, jdk11, liberica-jdk-full-bin, jdk-openjdk-xdg, jdk11-temurin, jdk17-temurin, jdk, zulu-11-bin, zulu-17-bin, jre-jetbrains, java-openjdk-ea-bin, jdk-openjdk, jdk11-openjdk, jdk17-openjdk, jdk8-openjdk)
Latest Comments
1 2 Next › Last »
kvbx commented on 2019-11-14 18:52 (UTC)
I've added a warning and instructions in case the build fails.
It's not possible (or at least feasible) to set JAVA_HOME during the build process, as there might be a lot of compatible JDKs. jdk8-openjdk and graal-bin for example work, but there might be more. I don't want to force the user to install e.g. jdk8-openjdk if she already has another compatible JDK installed.
gonciarz commented on 2019-11-14 18:34 (UTC)
I partially agree that devs can handle this issue but on the other hand creating a package should be fully automated.
kvbx commented on 2019-11-14 17:45 (UTC)
Neverlesess I think that users of this package are seasoned java developers and can get around this. Just set JAVA_HOME to a jdk supported by gradle 4.4 for the build process (e.g. jdk8).
gonciarz commented on 2019-11-14 13:06 (UTC) (edited on 2019-11-14 13:08 (UTC) by gonciarz)
kvbx commented on 2019-11-14 12:38 (UTC)
Currently the build uses gradlew which in this project is quite old (4.6) and doesn't even work with jdk11. We could use a newer gradle as makedep but this wouldn't work with jdk13 as well, as jdk13 support will land in gradle 6 and that's not released yet (docker won't help either). For the time being I'll stick to the original build process and add a makedep for java-environment<11. The resulting executable seems to run fine on jdk13 though.
gonciarz commented on 2019-11-12 23:09 (UTC)
I'm sorry guys but recently I didn't have time to update. I discovered an issue, that from my point of view should be addressed. The project is based on gradle4 however gradle in this version does not support jdk13. I think that we can't be bound to jdk <8,11). We may always use docker image for building but I'm not sure if that's not an overhead. Please suggest a gentle solution for that. I'm ready to disown package.
Svenstaro commented on 2019-11-08 10:00 (UTC)
You can file a request to disown the package.
kvbx commented on 2019-11-08 05:54 (UTC)
This has been out of date for more than 2 months. Don't want to push you, but should I take over?
kvbx commented on 2019-11-08 05:54 (UTC)
This has been out of date for more than 2 months. Don't want to push you, but should I take over?
Svenstaro commented on 2019-07-18 23:12 (UTC)
I don't really care. You can have the entire package. I don't really need this anymore.
1 2 Next › Last »