Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Java Minimum Version to JDK8 #65

Closed
martinei opened this issue May 9, 2018 · 5 comments · Fixed by #78
Closed

Update Java Minimum Version to JDK8 #65

martinei opened this issue May 9, 2018 · 5 comments · Fixed by #78

Comments

@martinei
Copy link
Contributor

martinei commented May 9, 2018

Stateless4J introduces a number of (Functional) Interfaces that are present in a similair form in the jdk since java 8 (Action1 -> Consumer, Action2 -> BiConsumer, Func -> Supplier, Func2 -> Function, Func3 -> BiFunction, FuncBoolean -> BooleanSupplier).

What do you think about updating to a more recent java, removing the duplicates and renaming some of the other interfaces to match the JDK Naming (e.g. Func4 -> TriFunction, Action3 -> TriConsumer)? Using the familiar names would make it easier for the reader.

@Ktar5
Copy link
Contributor

Ktar5 commented May 9, 2018

I'm not entirely sure about this, though I have thought about it. I'll leave this issue open for a while and see if there is any other expressed interest in this. If so, it'll happen, if not-- it's a non-issue.

@Ktar5 Ktar5 changed the title Update Java Version Update Java Minimum Version to JDK8 May 9, 2018
@binkley
Copy link

binkley commented Aug 3, 2019

I found this project through a GitHub issue in JUnit (junit-team/junit5#48 (comment)).

Given that Java 11 is the LTS version, and Java 13 is heading our way ... what is the maintenance status of this project? :)

@ezaquarii
Copy link
Collaborator

@martinei Since I took the maintainership, I'm open to modernization proposals. If you are interested in helping out, let me know.

@ezaquarii
Copy link
Collaborator

@binkley This project has been almost abandoned, but since I'm using it in other projects, I took ownership of it now. I'll try to gradually make it in better shape. Let me know if you are interested in helping out.

@ezaquarii
Copy link
Collaborator

There are 2 reasons why we'd like to keep old interfaces:

  1. existing users will be forced to migrate their solutions
  2. Android runtime pre API-24 still does not support many JDK8 classes and this is substantial developer demographic I'd like to support

I'll bump language to Java8 to enable use of language features, but I do not plan to refactor APIs in the near future.

ezaquarii added a commit that referenced this issue Sep 13, 2019
Closes #65

Signed-off-by: Chris Narkiewicz <hello@ezaquarii.com>
ezaquarii added a commit that referenced this issue Sep 13, 2019
Closes #65

Signed-off-by: Chris Narkiewicz <hello@ezaquarii.com>
ezaquarii added a commit that referenced this issue Sep 13, 2019
Closes #65

Signed-off-by: Chris Narkiewicz <hello@ezaquarii.com>
ezaquarii added a commit that referenced this issue Sep 13, 2019
Closes #65

Signed-off-by: Chris Narkiewicz <hello@ezaquarii.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants