Mailing-List: contact notifications-help@groovy.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.apache.org
Date: Sat, 16 Apr 2016 06:50:25 +0000 (UTC)
From: "Jochen Theodorou (JIRA)" <jira@apache.org>
To: notifications@groovy.apache.org
Message-ID: <JIRA.12816567.1348627280000.246314.1460789425501@Atlassian.JIRA>
In-Reply-To: <JIRA.12816567.1348627280000@Atlassian.JIRA>
References: <JIRA.12816567.1348627280000@Atlassian.JIRA>
 <JIRA.12816567.1348627280634@arcas>
Subject: [jira] [Commented] (GROOVY-5727) Ovverriding 3rd Party libraries
 shipped
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jochen Theodorou commented on GROOVY-5727:
------------------------------------------

not used by Groovy is a long stretch...

ant jars used by ant builder, as well as the ant groovy tasks
bsf is the bean scripting framework, which we have a plugin for in the distribution
jansi, jcommander, jline, commons-cli used by the command line programs
commons-logging used for logging
gpars extension to Groovy for concurrent programming
ivy used by Grape
jsr166y and multiverse-core are used by gpars
hamcrest/junit/testng used by Groovy test support
qdox used by groovydoc
xstream/xmlpull used by the different xml builders
servlet-api used by Groovy Servlet


I can see, that maybe we should not include servlet-api, but for the others you have to be a bit more precise of how you want someone use these components in a script or from commanline then

> 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)