[jira] [Resolved] (RANGER-96) Eliminate the need to manage the transitive and multi-version dependancies by hand during depadency phase

["Madhan Neethiraj (Jira)" <ji...@apache.org>]

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

Madhan Neethiraj resolved RANGER-96.
------------------------------------
    Resolution: Abandoned

> Eliminate the need to manage the transitive and multi-version dependancies by hand during depadency phase
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: RANGER-96
>                 URL: https://issues.apache.org/jira/browse/RANGER-96
>             Project: Ranger
>          Issue Type: Improvement
>    Affects Versions: 0.4.0
>            Reporter: Alok Lal
>            Priority: Minor
>              Labels: maven
>
> Currently we have to manage the multiple version of a dependency or transitive dependency by hand via specifying version numbers in the {{dependencySets}} during assembly phase.  For example all {{includes}} in the {{dependencySet}} of hbase-agent.xml file that have a version specified explicitly are cases where we are trying to hand control the multiple versions of transitive dependency from getting in.  ARGUS-95 might address with this issue.  This JIRA is to come back and clean up the vestiges from the assembly files.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)