You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Ramesh Mani (JIRA)" <ji...@apache.org> on 2015/10/28 19:03:27 UTC
[jira] [Resolved] (RANGER-586) Ranger plugins should not add
dependent libraries to component's CLASSPATH
[ https://issues.apache.org/jira/browse/RANGER-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramesh Mani resolved RANGER-586.
--------------------------------
Resolution: Fixed
> Ranger plugins should not add dependent libraries to component's CLASSPATH
> --------------------------------------------------------------------------
>
> Key: RANGER-586
> URL: https://issues.apache.org/jira/browse/RANGER-586
> Project: Ranger
> Issue Type: Bug
> Components: plugins
> Affects Versions: 0.5.0
> Reporter: Madhan Neethiraj
> Assignee: Ramesh Mani
> Attachments: Ranger-586_initial.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)