Keeping components on EOL Java versions like 7 is a hassle in general. Building can be harder. It also makes components a lot less attractive to new contribute.
Gary On Tue, Oct 19, 2021, 15:21 Michael Osipov <micha...@apache.org> wrote: > Am 2021-10-19 um 13:38 schrieb Gary Gregory: > > Hi All, > > > > I intend to create a release candidate for CLI 1.5 soon. This will be the > > last Java 7 release IMO and I plan on this being a simple kinde of > release, > > no big new feature. Feel free to look at Jira. > > Thank you for moving this forward! > > > Beyond that, the snapshot POM can go to Java 8. > > Why if this is maintenance only? Do you expect somewhat to add major > changes which require Java 8? Don't invest more time than necessary. > > > I am not sure if CLI has a future without a ton of work considering the > > feature gap with other FOSS projects like JCommander and Picocli. > > Insane! I though JOpt Simple I use is nice, but those are a complete new > level. I wouldn't call them lightweight because they have tons of > features, seriously. Giving it more thought and knowing that the are > approx. 10+ Java-based CLI parsers, I would agree with you to send CLI > to maintenance mode unless it can do something much better than > picocli/JCommander/JOpt Simple/you name it. > > Michael > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
