[
https://issues.apache.org/jira/browse/OOZIE-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15340580#comment-15340580
]
Robert Kanter commented on OOZIE-2530:
--------------------------------------
The problem is that while Oozie might not need jline, the components we run or
the user code they run might need them (or maybe only when certain features are
used). So we need to include it with components that _might_ need it, rather
than components that need it during compilation. This is the case with most
3rd party dependencies we add in the sharelibs. Given that nobody has been
filing JIRAs to add jline to any of the other components, I'd say that what we
currently have is correct. You should build Oozie with no changes, and look
for jline jar files to see which sharelibs should have it. It would then be a
good idea to look at the poms from those components to make sure we have the
correct version.
> 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)
