ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Madhan Neethiraj (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (RANGER-586) Ranger plugins should not add dependent libraries to component's CLASSPATH
Date Wed, 06 Jan 2016 01:45:39 GMT

     [ https://issues.apache.org/jira/browse/RANGER-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Madhan Neethiraj updated RANGER-586:
------------------------------------
    Issue Type: Improvement  (was: Bug)

> 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: Improvement
>          Components: plugins
>    Affects Versions: 0.5.0
>            Reporter: Madhan Neethiraj
>            Assignee: Ramesh Mani
>             Fix For: 0.5.1
>
>         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)

Mime
View raw message