Skip to content
This repository has been archived by the owner on Mar 17, 2021. It is now read-only.

info: shifting JDK major versions in build pipeline #642

Open
ohbus opened this issue Feb 5, 2021 · 1 comment
Open

info: shifting JDK major versions in build pipeline #642

ohbus opened this issue Feb 5, 2021 · 1 comment

Comments

@ohbus
Copy link
Contributor

ohbus commented Feb 5, 2021

Why do we setup JDK 8 after setting up JDK 11 in the pipeline.

And again we setup JDK 11 at the end.

It would be great if somebody can provide the explanation of this behavior in the build as this is not expected nor a good practice.

If there is any module like example-projects/example-project that needs to be tested with different JDKs and can be done with the help of matrix builds.

I can help setup this build to make it more streamlined.

@ohbus
Copy link
Contributor Author

ohbus commented Feb 5, 2021

As a matter of fact the sonar analysis is being done on JDK 8 and SonarCloud has dropped support for running analysis using JDK 8.

We will need to upgrade to JDK 11 eventually.

@ohbus ohbus changed the title info: shifting JDKs in build pipeline info: shifting JDK major versions in build pipeline Feb 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant