Open emeroad opened 4 years ago
It would be nice to have a version matching policy similar to maven version scheme.
https://maven.apache.org/pom.html#dependency-version-requirement-specification
// pseudocode
public class MongoPlugin implements ProfilerPlugin, TransformTemplateAware {
context.addVerionMatcher(new MavenManifestVersionMatcher("[2.0.0)"));
}
Dependency Mediation and Conflict Resolution https://cwiki.apache.org/confluence/display/MAVENOLD/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges
Version Range Specification https://maven.apache.org/enforcer/enforcer-rules/versionRanges.html
https://github.com/naver/pinpoint/pull/7077
I plan to add a feature to identify the version in the plugin. This feature can separate plugins for each version of lib. It has the advantage of making compilation and maintenance easy. e.g) mongo-db-plugin-2.x.jar, mongo-db-plugin-3.x.jar,
Jarfile can be obtained from ProtectionDomain of Transform API.