[hibernate-issues] [JIRA] (HSEARCH-3929) Use JDK11 by default when building Hibernate Search

[Yoann Rodière (JIRA)]

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A58fa1ced-171a-4c00-97e8-5d70d442cc4b ) *created* an issue

Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiYTk5M2ZkNDZlNDc1NDY1ODhmYzM4YWRhODlhZjE4ZjciLCJwIjoiaiJ9 ) / Task ( https://hibernate.atlassian.net/browse/HSEARCH-3929?atlOrigin=eyJpIjoiYTk5M2ZkNDZlNDc1NDY1ODhmYzM4YWRhODlhZjE4ZjciLCJwIjoiaiJ9 ) HSEARCH-3929 ( https://hibernate.atlassian.net/browse/HSEARCH-3929?atlOrigin=eyJpIjoiYTk5M2ZkNDZlNDc1NDY1ODhmYzM4YWRhODlhZjE4ZjciLCJwIjoiaiJ9 ) Use JDK11 by default when building Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH-3929?atlOrigin=eyJpIjoiYTk5M2ZkNDZlNDc1NDY1ODhmYzM4YWRhODlhZjE4ZjciLCJwIjoiaiJ9 )

Issue Type: Task Assignee: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A58fa1ced-171a-4c00-97e8-5d70d442cc4b ) Components: build Created: 27/May/2020 00:47 AM Fix Versions: 6.0.0.Beta-backlog-low-priority Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A58fa1ced-171a-4c00-97e8-5d70d442cc4b )

This is not about creating Java 11 bytecode; we need to stick to Java 8 bytecode for now, so that Hibernate Search can be used on older JDKs.

However, building on JDK8 is becoming increasingly difficult, and it will become worse. Sonarcloud.io, in particular, will stop supporting JDK8 on October 2020: https://sonarcloud.io/documentation/upcoming/

We should:

* Change the Jenkinsfile/pom to build with JDK11 by default, but still target Java 8 bytecode for the main source.
* Change the Jenkinsfile to run integration tests with JDK8 *on the artifacts created by JDK11* (see below)
* Remove support for building with JDK8, at least for the published artifacts (raise the minimum JDK in maven-enforcer-plugin).
* Remove configuration specific to JDK8/9/10 in the pom files, at least for the published artifacts.

For #2, two possible solutions:

* Create a two-step build (create the artifacts, then test them), which could prove challenging, but could also be a great first step towards a cleaner release pipeline (currently the tested artifacts are not the ones we release, though they are built from the same source code in the same environment).
* Have surefire/failsafe use a different JDK than the one used to run Maven when running tests. Probably easy to do, but the other solution is more powerful.

( https://hibernate.atlassian.net/browse/HSEARCH-3929#add-comment?atlOrigin=eyJpIjoiYTk5M2ZkNDZlNDc1NDY1ODhmYzM4YWRhODlhZjE4ZjciLCJwIjoiaiJ9 ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3929#add-comment?atlOrigin=eyJpIjoiYTk5M2ZkNDZlNDc1NDY1ODhmYzM4YWRhODlhZjE4ZjciLCJwIjoiaiJ9 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100127- sha1:a588176 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/hibernate-issues/attachments/20200527/cf0500e3/attachment.html