avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Carey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-1213) Dependency on Jetty Servlet API in IPC
Date Fri, 30 Nov 2012 19:18:02 GMT

    [ https://issues.apache.org/jira/browse/AVRO-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507574#comment-13507574

Scott Carey commented on AVRO-1213:

Optional is OK for now for Jetty, and Netty.  The use can choose which they want.  Optional
may require changing avro-tools' pom to declare those, and we'll need to document the change.
 I'd say it would need to wait until 1.8.0 because upgrading would break current projects,
and there is a work-around for users now to exclude jetty and/or the servlet downstream dependencies
in their pom.

Longer term, we could break up IPC into more modules, one for HTTP RPC and another for socket,
since the two have very different downstream dependencies.
> Dependency on Jetty Servlet API in IPC
> --------------------------------------
>                 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: Minor
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message