[
https://issues.apache.org/jira/browse/GROOVY-5727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17757462#comment-17757462
]
Paul King commented on GROOVY-5727:
-----------------------------------
The problem is still present if considering the Groovy standard install (which
I think is implicit although not mentioned). I don't think the maven artifacts
have ever had this problem (at least not to any significant degree). But I have
no problem closing the issue to see if the libs we currently ship with are
still causing folks problems - they can open a new issue and we can have a more
focussed discussion.
> 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
> Assignee: Jochen Theodorou
> Priority: Major
> Labels: contrib
> Fix For: 2.5.0
>
>
> 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
(v8.20.10#820010)
