[
https://issues.apache.org/jira/browse/PIG-5298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167730#comment-16167730
]
Adam Szita commented on PIG-5298:
---------------------------------
[~nkollar], if currently the only reason the pull in jetty is to make use of
its EL implementation which as you say in the newer versions is basically
borrowed from that of Glassfish the logical thing to do IMHO would be to use
just glassfish EL, no jetty and no tomcat.
I believe we should always try to reduce the number and size of dependent
libraries to only those that we actually make use of.
> Verify if org.mortbay.jetty is removable
> ----------------------------------------
>
> Key: PIG-5298
> URL: https://issues.apache.org/jira/browse/PIG-5298
> Project: Pig
> Issue Type: Improvement
> Affects Versions: 0.17.0
> Reporter: Adam Szita
> Assignee: Nandor Kollar
> Attachments: PIG-5298_1.patch
>
>
> Although we pull in jetty libraries in ivy Pig does not depend on
> org.mortbay.jetty explicitly. The only exception I see is in Piggybank where
> I think this can be swapped by javax.el-api and log4j.
> We should investigate (check build, run unit tests across all exec modes) and
> remove if it turns out to be unnecessary.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
