[jira] [Commented] (GROOVY-5727) Ovverriding 3rd Party libraries shipped

["Siegfried Goeschl (JIRA)" <ji...@apache.org>]

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

Siegfried Goeschl commented on GROOVY-5727:
-------------------------------------------

Just spend the better part of the evening with getting an servlet-api-2.4.jar 

* Playing with Groovy 2.4.7 & Apache Camel 2.17.2
* Invoked camel-jetty which requires servlet-api-3.x
* Grab does not overwrite servlet-api-2.4.jar 

During the execution I get the following errors

{code}
java.lang.NoSuchMethodError: javax.servlet.http.HttpServletRequest.isAsyncStarted()
java.lang.NoSuchMethodError: javax.servlet.http.HttpServletResponse.getStatus()
{code}

IMHO upgrading to servlet-api-3.1 would be sensible since 2.4 stems from 2005

> Ovverriding 3rd Party libraries shipped
> ---------------------------------------
>
>                 Key: GROOVY-5727
>                 URL: https://issues.apache.org/jira/browse/GROOVY-5727
>             Project: Groovy
>          Issue Type: Improvement
>          Components: Groovysh
>    Affects Versions: 2.0.4
>            Reporter: deas
>              Labels: contrib
>
> Groovy 2.0.4 ships various 3rd party libraries, e.g. servlet-api-2.4.jar and jsp-api-2.0.jar. These can get in the way and I see no reasonable way to use user defined versions in groovysh. Of course you can introduce a custom classloader searching locally before delegating to the parent or just remove the library shipped to get it out of the way, but I feel there should be a groovier way. Maybe you should just omit shipping these libraries.
> A concrete situation where I encountered this problem was when I wanted a groovy script to launch jetty with servlet 3.0 support, pulling in various dependencies with Grape.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)