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: | |
Submitter: | Svenstaro |
Maintainer: | None |
Last Packager: | kvbx |
Votes: | 2 |
Popularity: | 0.000075 |
First Submitted: | 2019-06-21 09:01 |
Last Updated: | 2020-05-25 09:50 |
Dependencies (1)
- java-environment>=8 (jdk5, tuxjdk, jdk7-openjdk-infinality, java-8-openjdk-shenandoah, jdk8-openjdk-infinality, java-gcj-compat, jdk9, zulu-10-bin, jdk-devel, jdk8-arm64, jdk6, jdk12-openj9-bin, zulu-12-bin, jdk12, jdk8-openjdk-dcevm, jdk11-graalvm-ee-bin, jdk8-arm, jdk13-openj9-bin, jdk9-openj9-bin, jdk10, jdk11-openjdk-dcevm, jdk8-openjdk-jetbrains, jdk8-openjdk-shenandoah, jdk10-openj9-bin, jdk14-openj9-bin, jdk7, jdk8-jetbrains, jdk7r1-j9-bin, jdk7-j9-bin, zulu-14-bin, zulu-13-bin, jdk-bcl, amazon-corretto-15, jdk-openj9, jdk11-openj9-bin, java-openjdk-bin, amazon-corretto-8, amazon-corretto-11, jdk11-openjdk-dcevm-conflicts-fixed, jdk8, jdk-openj9-bin, jdk, jdk11-adoptopenjdk, jdk-adoptopenjdk, zulu-8-bin, zulu-11-bin, zulu-15-bin, liberica-jdk-11-bin, liberica-jdk-11-lite-bin, liberica-jre-11-full-bin, liberica-jdk-8-full-bin, liberica-jdk-full-bin, liberica-jdk-11-full-bin, liberica-jre-11-bin, liberica-jre-8-full-bin, zulu-embedded-jdk, jdk8-j9-bin, zulu-embedded-jdk11, jdk8-openj9-bin, zulu-embedded-jdk8, jdk11, sapmachine-jdk-bin, jdk11-jetbrains-imfix, jre-jetbrains, jdk11-graalvm-bin, jdk8-graalvm-bin, jdk8-adoptopenjdk, java-openjdk-ea-bin, java-openjdk-loom-ea-bin, jdk-arm, jdk-jetbrains, jdk-openjdk, jdk11-openjdk, jdk7-openjdk, jdk8-openjdk)
Latest Comments
1 2 Next › Last »
kvbx commented on 2019-11-14 18:52
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
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
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
kvbx commented on 2019-11-14 12:38
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
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
You can file a request to disown the package.
kvbx commented on 2019-11-08 05:54
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
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
I don't really care. You can have the entire package. I don't really need this anymore.