[
https://issues.apache.org/jira/browse/OOZIE-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398118#comment-15398118
]
Thomas Poepping commented on OOZIE-2530:
----------------------------------------
Pig directly depends on jline as a compile dependency. In my testing, it looks
like the pig sharelib should transitively load the required jline dependency
from the dependency on org.apache.pig, removing the requirement for the
explicit dependency.
The reason for this patch is that other sharelibs (like Hive) also depend on
jline, but on a later incompatible version. If there is an explicit dependency
defined in the root pom, then the transitive jline dependency loaded from the
hive jars for the hive sharelib will be managed to the incompatible version,
causing Hive actions to fail.
Does Oozie not have any integration tests that install oozie, install the
sharelib, and run through the examples? That would answer our question.
> Remove jline from parent and sharelib pig pom
> ---------------------------------------------
>
> Key: OOZIE-2530
> URL: https://issues.apache.org/jira/browse/OOZIE-2530
> Project: Oozie
> Issue Type: Improvement
> Affects Versions: trunk
> Reporter: Thomas Poepping
> Attachments: OOZIE-2530.01.patch, OOZIE-2530.patch
>
>
> This patch removes an unnecessary hardcoded dependency on jline in the oozie
> parent pom and pig sharelib pom.
> The jline dependencies were required before OOZIE-704, which removed the
> direct dependencies on jline in oozie code. Since that patch, the direct
> dependency on jline in oozie has been unnecessary. This will also fix
> OOZIE-2409.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
