You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/09/08 18:51:00 UTC
[jira] [Commented] (AVRO-1213) Revisit dependencies on Jetty,
servlet-api, and Netty
[ https://issues.apache.org/jira/browse/AVRO-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16159099#comment-16159099 ]
ASF GitHub Bot commented on AVRO-1213:
--------------------------------------
GitHub user dkulp opened a pull request:
https://github.com/apache/avro/pull/244
[AVRO-1213] Update to latest release of Jetty
This updates the Jetty dependency to the latest Jetty release.
Note: this does not address the Jetty vs. Netty thing or updates to the latest Netty. I hope to tackle that soon, but the netty update is huge/hard with a much larger impact.
The API signatures do change slightly, but that is obviously required due to the org.mortbay -> org.eclipse change. However, getting onto the supported version of Jetty (with the latest security updates and fixes) is important.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dkulp/avro JETTY
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/avro/pull/244.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #244
----
commit b9ea20ba5700a7df60411a7bd62406f5c4beab42
Author: Daniel Kulp <dk...@apache.org>
Date: 2017-09-08T17:18:33Z
[AVRO-1213] Update to latest release of Jetty
----
> Revisit dependencies on Jetty, servlet-api, and Netty
> -----------------------------------------------------
>
> Key: AVRO-1213
> URL: https://issues.apache.org/jira/browse/AVRO-1213
> Project: Avro
> Issue Type: Improvement
> Components: java
> Affects Versions: 1.7.2
> Reporter: Sharmarke Aden
> Priority: Blocker
> Fix For: 1.9.0
>
>
> The compile scoped dependency on jetty servlet-api in the IPC pom file can be problematic if using Avro in a webapp environment. Would it be possible to make this dependency either optional or provided? Or maybe Avro modularize into sub-modules in such a way that desired features can be assembled piecemeal?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)