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

Multiple binary variants for JDK 6/7/8 #41

Closed
robfletcher opened this issue May 29, 2018 · 2 comments
Closed

Multiple binary variants for JDK 6/7/8 #41

robfletcher opened this issue May 29, 2018 · 2 comments
Labels
🙄 chore Infrastructure or build related 🙅‍♀️ wontfix This will not be worked on
Projects
Milestone

Comments

@robfletcher
Copy link
Owner

No description provided.

@robfletcher robfletcher added the 🙄 chore Infrastructure or build related label May 29, 2018
@robfletcher robfletcher added this to the v1.0 milestone May 29, 2018
@robfletcher robfletcher added this to To do in Release 1.0 Jul 20, 2018
@Ray-Eldath
Copy link

Ray-Eldath commented Apr 10, 2020

Just about to propose a new issue for Java 1.6 support... Currently I'm transforming a library which is still using the somewhat legacy assert function called Ktorm, and the library is still targeting Java 1.6 for compability... so my refactor process can't go on due to the incosistency between the target platform of Strikt and Ktorm, which prohibit the usage of inline function, e.g. isA and expectThrows. Really hope Strikt, as a fundamental assertion library, could target multiple versions soon.

I don't know whether there's some automation tool to simplify such transition, like automatically remove inline modifier cause it'll not affact the main logic...? If not then this will be a chore... Anyway, really appreciating your efforts of creating and maintaining such a convinent library! 😉

@robfletcher
Copy link
Owner Author

Kotlin 1.8 no longer supports JVM targets < 8 so I'm closing this.

Release 1.0 automation moved this from To do to Done Jan 10, 2023
@robfletcher robfletcher added the 🙅‍♀️ wontfix This will not be worked on label Jan 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🙄 chore Infrastructure or build related 🙅‍♀️ wontfix This will not be worked on
Projects
Release 1.0
  
Done
Development

No branches or pull requests

2 participants