Thanks for reporting it. That’s an issue in the Versions Node Monitors plugin . I hope that we’ll submit a pull request to correct it as part of the She Code Africa Contributhon “Inclusive Naming” project.
If you’re interested in submitting a pull request to fix it, the file that needs the change is:
VersionMonitor.DisplayName=Remoting Version
VersionMonitor.OfflineCause=This node is offline because it uses an old slave.jar
VersionMonitor.MarkedOffline=Making {0} offline temporarily due to the use of an old slave.jar
JVMVersionMonitor.DisplayName=JVM Version
JVMVersionMonitor.OfflineCause=This node is offline because the JVM version of the agent is incompatible with the Master one.
JVMVersionMonitor.MarkedOffline=Making {0} offline temporarily due to using an incompatible JVM version between agent and master (master={1}, agent={2})
JVMVersionMonitor.RUNTIME_GREATER_OR_EQUAL_MASTER_BYTECODE=Agent runtime must be greater or equal than the Master bytecode level (strongly recommended minimum)
JVMVersionMonitor.MAJOR_MINOR_MATCH=Agent major.minor must be equal to Master major.minor JVM version (paranoid version)
JVMVersionMonitor.EXACT_MATCH=Agent JVM version must be exactly the same as Master JVM version (paranoid++ version)
JVMVersionMonitor.UnrecognizedAgentJVM=The agent JVM version {0} is not recognized by the plugin. You might want to open a ticket for the maintainer to complete the compatibility list.