Installation of Ranger plugin adds libraries that are used by the plugin into component’s CLASSPATH. For example, libraries like - gson, httpmime, eclipselink, javax.persistence, etc. This can potentially impact the functioning of the component if the component requires a version of a library which is incompatible with the version used by Ranger plugin.
One approach to minimize such impact is to have the Ranger plugin load the dependent libraries dynamically in its own class loader, instead of copying them to the component’s CLASSPATH.
- relates to
RANGER-715 Fix issues reported by coverity test in Ranger Plugin ClassLoader