Replies: 1 comment 1 reply
-
I'm not thinking about this in terms of vendor support. There may be people who are, for some reason, stuck on Java 5. What is the drawback of supporting that use case? How painful is it to ensure that picocli can be used on Java 5? And the answer so far is that there's nothing that I want to do that I can't do on Java 5. So why not support Java 5? If it becomes too painful I'll reconsider but so far I see no reason to require Java 6 or 8 or whatever... |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello there,
In the CONTRIBUTING.md file, we can see the following table:
picocli
picocli-codegen
picocli-groovy
picocli-shell-jline2
picocli-shell-jline3
picocli-spring-boot-starter
What's the reason for keeping a java 5 language version compatibility when no vendor supports that version anymore?
According to https://en.wikipedia.org/wiki/Java_version_history#Release_table, we could at least raise it to java 6 if we consider Azul, or 8 otherwise.
WDYT?
Beta Was this translation helpful? Give feedback.
All reactions