[jira] [Updated] (PIG-5298) Verify if org.mortbay.jetty is removable

2017-09-21 Thread Adam Szita (JIRA)

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

Adam Szita updated PIG-5298:

   Resolution: Fixed
Fix Version/s: 0.18.0
   Status: Resolved  (was: Patch Available)

> 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
> Fix For: 0.18.0
>
> Attachments: PIG-5298_1.patch, PIG-5298_2.patch, PIG-5298_3.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)


[jira] [Updated] (PIG-5298) Verify if org.mortbay.jetty is removable

2017-09-20 Thread Nandor Kollar (JIRA)

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

Nandor Kollar updated PIG-5298:
---
Attachment: PIG-5298_3.patch

> 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, PIG-5298_2.patch, PIG-5298_3.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)


[jira] [Updated] (PIG-5298) Verify if org.mortbay.jetty is removable

2017-09-18 Thread Nandor Kollar (JIRA)

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

Nandor Kollar updated PIG-5298:
---
Attachment: PIG-5298_2.patch

> 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, PIG-5298_2.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)


[jira] [Updated] (PIG-5298) Verify if org.mortbay.jetty is removable

2017-09-06 Thread Nandor Kollar (JIRA)

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

Nandor Kollar updated PIG-5298:
---
Status: Patch Available  (was: Open)

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


[jira] [Updated] (PIG-5298) Verify if org.mortbay.jetty is removable

2017-09-06 Thread Nandor Kollar (JIRA)

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

Nandor Kollar updated PIG-5298:
---
Attachment: PIG-5298_1.patch

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


[jira] [Updated] (PIG-5298) Verify if org.mortbay.jetty is removable

2017-09-05 Thread Adam Szita (JIRA)

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


[jira] [Updated] (PIG-5298) Verify if org.mortbay.jetty is removable

2017-09-05 Thread Adam Szita (JIRA)

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

Adam Szita updated PIG-5298:

Affects Version/s: 0.17.0

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



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)