[
https://issues.apache.org/jira/browse/GROOVY-5727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407349#comment-15407349
]
Paul King edited comment on GROOVY-5727 at 8/4/16 7:36 AM:
-----------------------------------------------------------
I upgraded to 3.0.1 for the master branch (upcoming 2.5 release): GROOVY-7899
The 3.1 api contains a breaking change. We'd have to be careful to make sure we
don't impact legacy users. There is possibly no problem but I haven't
investigated yet so went with the more conservative 3.0.1.
was (Author: paulk):
I upgraded to 3.0.1 for the master branch (upcoming 2.5 release).
The 3.1 api contains a breaking change. We'd have to be careful to make sure we
don't impact legacy users. There is possibly no problem but I haven't
investigated yet so went with the more conservative 3.0.1.
> 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)
