With Deploy (and Release) 24.X, there is a plugin validation script included to check that any plugins are compatible with JDK17. The final output from this is something like:
-------------------------------------------------------------------------------------------
The following plugins are not compatible with JDK17:
deploy_plugin-1
deploy_plugin-2
However, it does not list out *why* the plugins are not compatible, and neither does any of the logged output from executing the validation script. It would have been extremely helpful if such information had been provided, rather than users spending days manually pulling apart their XLDPs + JARs to trace through all the dependencies to find out what *might* be the culprit.
by: Peter G. | 5 months ago | User interface
Comments
The official plugins bundled with Digital.ai Release and Deploy products should be JDK17 compliant. If you notice any unexpected behavior, please inform our Customer Support.
For custom plugins, the validator tool detects if the code imports Javax libraries that are no longer compliant and notifies users. We recommend searching for "Javax" within the custom plugin code and checking our recommendations to guide you in updating the code (https://docs.digital.ai/bundle/devops-release-version-v.24.1/page/release/release-notes/releasemanual_release_v.24.1.html#jdk-migration-java-17-support). External libraries that use unsupported Javax may also need manual updates, but these cannot be easily detected.