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.

Sign up for GitHub

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

Jump to bottom

Make it easier to use a different JVM target #297

Closed
wants to merge 2 commits into from
Closed

Make it easier to use a different JVM target #297

wants to merge 2 commits into from

Commits on Aug 4, 2022

  1. Make it easier to use a different JVM target 

    Whilst Jenkins defaults will now be java11 some libraries may want to
stay on java8.

Doing so makes backports of any issues much easier (hopefully not
needed!) and the library can take advantage of all the updated plugins
with their fixes.

Whilst this is less than optimal for java8 as it still required a java9+
JVM to be used to compile (as that was when the `release` flag was
introduced it is much better than either pinning the parent to 1.76 (the
last supporting java8), or having to overwrite all the properties to
remove the maven.compiler.release and testRelease ones as well as
overwriting the enforcer configurations (albeit this is simplier with
combine.children)
    @jtnord
    jtnord committed Aug 4, 2022
    Configuration menu
    Copy the full SHA
    989be0d View commit details
    Browse the repository at this point in the history

  2. Update pom.xml 

    Co-authored-by: Jesse Glick <jglick@cloudbees.com>
    @jtnord @jglick
    jtnord and jglick committed Aug 4, 2022
    Configuration menu
    Copy the full SHA
    7f07696 View commit details
    Browse the repository at this point in the history