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

Drop support for Java 7 #70

Closed
szpak opened this Issue Nov 14, 2017 · 2 comments

Comments

Projects
None yet
1 participant
@szpak
Owner

szpak commented Nov 14, 2017

Java 7 has been EOLed years ago, it's not easily accessible from Oracle, it is deprecated in Gradle 4 and there are issues in using it on Travis.

  • - display warning for Java 7 users
  • - document ability to build with Java 7 while running Gradle with Java 8
  • - switch artifacts compatibility to Java 8
@szpak

This comment has been minimized.

Owner

szpak commented Dec 20, 2017

Newer Gradle 4 versions display deprecation warning about Java 7 which breaks the functional tests (which check for deprecated stuff).

@szpak szpak added this to the 1.3.0 milestone Dec 20, 2017

szpak added a commit that referenced this issue Jan 27, 2018

[#70] Drop support for Java 7
Released binary artifacts require at least Java 8.
@szpak

This comment has been minimized.

Owner

szpak commented Jan 27, 2018

Issues with Java 7:

  • deprecated as of April 2016
  • deprecated in Gradle 4
  • issues issues related to maintaining of regression test harness with different Java versions (some Gradle/PIT version are not Java 9 compatible, some Gradle version doesn't like Java 7 builds)
  • limited availability of Java 7 on CI servers

The Java 7 support has been terminated as of gradle-pitest-plugin 1.3.0 (as a JDK version required to run a Gradle build). The latest version with Java 7 compatible binaries is 1.2.4.

@szpak szpak closed this Jan 27, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment