Fix Java 17 compatibility issue with reflection access to Field.modifiers #328
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix Java 17 compatibility issue causing agent launch failures
Problem
The EnvInject plugin fails to launch agents on Java 17+ environments due to module system restrictions. The error occurs when the plugin attempts to access internal JDK reflection APIs that are no longer accessible without explicit module opens.
Error seen:
Root Cause
Field.class.getDeclaredField("modifiers")finalmodifier onEnvVars.masterEnvVarsfield--add-opensSolution
Implemented a graceful fallback mechanism that:
NoSuchFieldExceptionandIllegalAccessExceptiongracefullyEnvVars.masterEnvVars.putAll()instead of field replacementCode Changes
EnvInjectMasterEnvVarsSetter.getModifiers()to handle missing modifiers fieldcall()method to gracefully handle reflection failuresclear()+putAll()Testing done
Executed all unit tests
Have installed into a Jenkins instance and used the plugin. Tested agent launch logs with and without the fix:

Without Fix
With Fix

Submitter checklist