You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@avro.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2012/11/30 18:35:59 UTC

[jira] [Commented] (AVRO-1213) Dependency on Jetty Servlet API in IPC

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

Doug Cutting commented on AVRO-1213:
------------------------------------

Optional sounds reasonable to me.  It's hard to use a servlet without having that provided and we shouldn't mandate a particular source for the servlet api.

And shouldn't the other Jetty dependencies be for tests only?
                
> 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