pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Szita (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PIG-5298) Verify if org.mortbay.jetty is removable
Date Tue, 05 Sep 2017 09:34:00 GMT

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

Adam Szita updated PIG-5298:
----------------------------
    Description: 
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.

  was:
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 and remove if it turns out to be unnecessary.


> 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
>
> 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)

Mime
View raw message