[
https://issues.apache.org/jira/browse/ATLAS-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated ATLAS-987:
-----------------------------------
Fix Version/s: 0.7.1-incubating
Committed to 0.7-incubating branch:
http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/d6f3ab72876ca5505ba78bc8cb3dc3f3e407fec1
> Atlas hooks should avoid adding dependent libraries to component CLASSPATH
> --------------------------------------------------------------------------
>
> Key: ATLAS-987
> URL: https://issues.apache.org/jira/browse/ATLAS-987
> Project: Atlas
> Issue Type: Bug
> Reporter: Madhan Neethiraj
> Assignee: Madhan Neethiraj
> Fix For: 0.8-incubating, 0.7.1-incubating
>
> Attachments: ATLAS-987-v6.patch, ATLAS-987.2.patch,
> ATLAS-987.3.patch, ATLAS-987.4.patch, ATLAS-987.5.patch, ATLAS-987.patch
>
>
> Libraries used by Atlas hooks (like json, commons-configuration,
> commons-logging, etc) are added to component’s CLASSPATH. This can
> potentially impact the functioning of a component if the component requires a
> version of a library which is incompatible with the version used by Atlas
> hook.
> One approach to minimize such impact is to have Atlas hooks load the
> dependent libraries in its own class loader, instead of copying them to the
> component’s CLASSPATH. This will restrict the dependent libraries to be
> visible only to Atlas hooks, there by isolating the component from these
> libraries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
