Adding Version Constraints for Target Libraries in Java Agent Instrumentation

[CodePrometheus]

Description

In Java Agent, we already have witnessClasses and witnessMethods, which can play a limiting role when the target may have multiple versions. From the perspective of plugin developers, these operations may be more expensive or not simple enough (I think) than directly determining the version, so I want to add a witnessVersion to directly limit the target libraries version.

For example, I can apply the following restrictions to pulsar-client (version 4.x):

@Override
protected WitnessVersion witnessVersion() {
    return WitnessVersion.of(targetVersionGte("4.0.0"));
}

The implementation plan is as follows:
Using the ProtectionDomain protectionDomain in the method parameters of transform, we can get the target jar info through getCodeSource().getLocation().

1. Get the version in META-INF/maven/../pom.properties through groupId, artifactId (higher priority)
2. Get Implementation-Version through Manifest

Are you willing to submit a pull request to implement this on your own?

• Yes I am willing to submit a pull request on my own!

Code of Conduct

• I agree to follow this project's Code of Conduct

[wu-sheng]

I think the key question is, why? Which scenario will require this? Because the version is something more random by the developers, what is the reason we need to trust that? The version number level backward compatibility usually means from user APIs and API usage perspective, but the agent focuses on the core codes. They are different.