graalvm-reachability-metadata
picocli
graalvm-reachability-metadata | picocli | |
---|---|---|
8 | 29 | |
327 | 4,714 | |
2.1% | - | |
8.6 | 8.8 | |
6 days ago | 9 days ago | |
Java | Java | |
Creative Commons Zero v1.0 Universal | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
graalvm-reachability-metadata
-
GraalVM for JDK 21 is here
gcj had a lot of problems beyond needing configuration of reflection metadata. It used a full reimplementation of the standard library, and it was never adopted by the wider Java community being largely just Red Hat's strategy for creating a fully open source Java implementation rather than something offering specific benefits to Java developers. In particular people thought it'd lead to faster code, but GCC was never designed for Java and the results were actually a fair bit slower iirc.
Native image is quite different. With this new release the compiled images can not only be faster than JIT compiled Java (wow) but also use way less memory and start instantly. At a stroke this is resolving one of the biggest complaints people have always had against JVM languages.
And as a consequence you're seeing adoption by the wider community. All the modern Java web frameworks support it now, and there's a metadata repository where it's collected for projects that haven't accepted it upstream yet [1].
[1] https://github.com/oracle/graalvm-reachability-metadata
-
Are there any poplar alternatives to siesta?
Yeah, I was able to get it working by adding some custom runtime hints. jOOQ support was recently added to the graalvm-reachability-metadata repo via this issue, so that may make things easier
-
Spring Boot 3 meets Graal Native Image
During native image generation, native-image tool does a static analysis. There are classes which might not get accessed during this static analysis and they get left out in the final artifact. To overcome this some extra information can be provided during build time. Creating this extra metadata is cumbersome. There's an effort to consolidate these metadata information for various 3rd party libraries into a shared github repo https://github.com/oracle/graalvm-reachability-metadata .
-
Oracle Contributing GraalVM Community Edition Java Code to OpenJDK
GraalVM is truly great stuff.
GraalVM native compilation helps Java in the data center to avoid being a cost sink and to reduce start-up latency. Oracle needs Java to sell enterprise software.
Oracle contributing to OpenJDK may be required for Amazon cooperation (since Amazon is pushing its own JDK build) and probably helps the library ecosystem work towards native compatibility.
Native support for reflection (used in many libraries) requires "reachability metadata), maps of reflective API usage, at build time. Anyone can do it, but enterprise requires authoritative sources. Until authoritative reachability metadata covers the transitive graph of library+version dependencies in enterprise software, GraalVM builds are a PITA.
- https://github.com/oracle/graalvm-reachability-metadata
- latest release: https://medium.com/graalvm/graalvm-22-3-is-here-jdk-19-build...
- graalvm "community" roadmap: https://github.com/orgs/oracle/projects/6
(As a side note: Mark Reinhold has run the JDK team since 1997: is there any comparable example of such stellar leadership for broadly-adopted software across multiple technical and organizational eras?)
-
GraalVM 22.3: JDK 19 builds, jlink support, new monitoring features, and more
Also, reflection is supported in AOT mode. The analysis, however, does require reachability metadata in some cases. In the best case, libraries provide and maintain appropriate configuration for this. Reachability metadata can also be shared via https://github.com/oracle/graalvm-reachability-metadata.
-
is anyone using graal/spring native in production?
Most JVM libraries will require some amount of reflection for all frameworks as well, and for that we have made the bet to invest on a JVM wide effort -> https://github.com/oracle/graalvm-reachability-metadata.
-
Current State of Spring Boot Native with Kotlin (GraalVM)
The first issue should be solvable by refining Kotlin hints in https://github.com/oracle/graalvm-reachability-metadata that is used for non Spring hints with Boot 3.
picocli
-
GraalVM for JDK 21 is here
Picocli allows using a compiler annotation processor to generate classes at compile time instead [0].
[0]: https://github.com/remkop/picocli/blob/main/picocli-codegen/...
-
Any library you would like to recommend to others as it helps you a lot? For me, mapstruct is one of them. Hopefully I would hear some other nice libraries I never try.
Picocli is a pretty good one for writing CLI apps
-
“Why I develop on Windows”
"and there are simply no good command line input parsing libraries for Java."
Looks like author missed the most obvious and popular OSS one: https://picocli.info/
-
Java 20 / JDK 20: General Availability
The command line example gave me the "ick". It is usually preferrable to parse the command line arguments into one instance of a custom "command class", rather than into a list of things. Like jcommander, picocli or jbock do.
-
any opinion good or bed about a code that smells?
Complex argument parsing needs to be auto-generated by libraries like picocli. Even if you need something custom, it'd be quicker to write an Annotation processor from scratch than editing that file.
-
Owl: A toolkit for writing command-line user interfaces in Elixir
https://github.com/remkop/picocli
"Picocli-based applications can be ahead-of-time compiled to a GraalVM native image, with extremely fast startup time and lower memory requirements, which can be distributed as a single executable file."
https://picocli.info/quick-guide.html
-
Building a Java CLI. How can I make it more powershell-friendly
Using picocli to handle your command line options gives you the best chance to automatically generate an ArgumentCompleter script in the future, but won't help you today (other than possibly making your command line handling more standardized & easier).
-
must known frameworks/libs/tech, every senior java developer must know(?)
Picocli
-
🔍 Validate New-Caledonia Phone Numbers from cli ⌨️
Then we released a JBang! and picocli based cli that would be, on any OS running a jvm runtime :
-
📲 Inspired by Twilio we started to build our own (pico)cli to send sms
picocli : "a mighty tiny command line interface"
What are some alternatives?
Spring - Spring Framework
Spring Shell 3 - Spring based shell
daobab-100plus-examples - Daobab examples in Java
JCommander - Command line parsing framework for Java
jOOQ - jOOQ is the best way to write SQL in Java
args4j - args4j
coffee4j-back-end - The back-end of an application for tracking your coffee brews
Airline - Java annotation-based framework for parsing Git like command line structures
httpserver
JLine - JLine is a Java library for handling console input.
spring-aot-smoke-tests - Smoke tests for Spring's AOT and native support
JewelCLI - JewelCli uses an annotated interface definition to automatically parse and present command line arguments