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-compatAUR, jdk12AUR, jdk9-openj9-binAUR, jdk10AUR, jdk10-openj9-binAUR, jdk7AUR, zulu-14-binAUR, amazon-corretto-15AUR, sapmachine-jdk-binAUR, amazon-corretto-16AUR, jdk8-graalvm-binAUR, jdk16-graalvm-binAUR, jdk16-adoptopenjdkAUR, jdk16-microsoft-openjdkAUR, jdk11-msopenjdk-binAUR, jdk8-armAUR, jdk17-jetbrainsAUR, liberica-jre-11-binAUR, jdk11-jetbrains-imfixAUR, java-openjdk-loom-ea-binAUR, jdk11-j9-binAUR, jdk11-jbr-xdgAUR, jdk16-openjdkAUR, jdk13-openjdkAUR, jdk14-openjdkAUR, amazon-corretto-18AUR, bishengjdk-17AUR, jdk-armAUR, jdk11-openj9-binAUR, jdk-openj9-binAUR, jdk-jbr-xdgAUR, jdk18-openjdkAUR, jdk-android-studioAUR, amazon-corretto-19-binAUR, jdk19-graalvm-binAUR, liberica-jre-11-full-binAUR, jdk19-graalvm-ee-binAUR, jdk13-openjdk-binAUR, zulu-embedded-jdkAUR, jabba-binAUR, jdk15-openjdkAUR, liberica-jre-8-full-binAUR, jdk11-graalvm-binAUR, jdk19-openjdkAUR, jdk11-microsoft-openjdkAUR, jdk-openj9AUR, jdk11-graalvm-ee-binAUR, jdk17-jetbrains-imfixAUR, jdk11-openjdk-dcevmAUR, jdk12-openjdkAUR, jdk8-dragonwell-extendedAUR, jdk-jetbrainsAUR, jdk11-dragonwell-standard-binAUR, jdk11-jetbrains-binAUR, jdk20-graalvm-binAUR, jdk17-graalvm-binAUR, jdk8-graalvm-ee-binAUR, jdk8-aarch64AUR, jdk8-adoptopenjdkAUR, amazon-corretto-20-binAUR, zulu-15-binAUR, jdk21-jetbrains-binAUR, jdk21-jetbrains-imfixAUR, jdk17-openj9-binAUR, jdk20-openj9-binAUR, jdk-openjdk-xdgAUR, jdk-microsoft-openjdkAUR, jdk17-microsoft-openjdkAUR, zulu-13-binAUR, java-openjdk-binAUR, zulu-jdk-fx-binAUR, amazon-corretto-11AUR, amazon-corretto-8AUR, zulu-11-binAUR, zulu-21-binAUR, amazon-corretto-21-binAUR, amazon-corretto-17AUR, zulu-8-binAUR, zulu-17-binAUR, liberica-jdk-8-full-binAUR, liberica-jdk-full-binAUR, jdk8-dragonwell-extended-binAUR, jdk8-dragonwell-standard-binAUR, jdk11-dragonwell-extended-binAUR, jdk17-dragonwell-standard-binAUR, jdk8-temurinAUR, jdkAUR, jdk-ltsAUR, jdk17-graalvm-ee-binAUR, jdk20-graalvm-ee-binAUR, jdk21-graalvm-ee-binAUR, jdk11-temurinAUR, jdk17-temurinAUR, jdk-temurinAUR, liberica-jdk-11-binAUR, liberica-jdk-11-lite-binAUR, liberica-jdk-11-full-binAUR, liberica-jdk-17-full-binAUR, jdk21-graalvm-binAUR, jre-jetbrainsAUR, mandrel-binAUR, jdk11AUR, jdk8AUR, jdk17-zulu-prime-binAUR, jdk8-openj9-binAUR, jdk17-jetbrains-binAUR, jdk8-j9-binAUR, jdk7-j9-binAUR, jdk7r1-j9-binAUR, java-openjdk-ea-binAUR, 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 »