Grape and loading classes that extend java.lang.Exception from compiled Groovy bytecode

Maybe someone can point me in the right direction regarding the following issue with Grape... Issue in code (in words further below): -- import org.codehaus.groovy.control.CompilerConfiguration def demoScriptText = """\ @Grab('org.apache.commons:commons-email:1.3.3') import org.apache.commons.

Re: Grape and loading classes that extend java.lang.Exception from compiled Groovy bytecode

PS: Below is what I get when I look at the Demo.class with the "JD" decompiler... Is this maybe some kind of Grape concurrency issue similar to GROOVY-7407? https://issues.apache.org/jira/browse/GROOVY-7407 (I still get the same result when I am applying the workaround listed there - which

Re: [VOTE] Release Groovy 2.4.9

Hi Daniel, I won't include your vote in the official vote count since it was neither a veto nor a +1 on the proposed artifacts as per Apache voting: http://apache.org/foundation/voting.html But we'll no doubt do a 2.4.10 soon and we can merge the change for GROOVY-8085 into that release. Cheers, P

[RESULT][VOTE] Release Groovy 2.4.9

The Apache Groovy 2.4.9 vote is now closed and has passed with 4 binding +1s and no 0 or -1: Binding votes +1s: Paul King John Wagenleiter Guillaume Laforge Jim Jagielski The Apache Groovy community will proceed with the release. Thanks, The Apache Groovy Team

答复: [VOTE] Release Groovy 2.4.9

Hi Paul, It does not matter. Feel free to release 2.4.9 😉 Cheers, Daniel.Sun 发件人: paulk_asert [via Groovy] 发送时间: 2017年2月27日 20:07 收件人: Daniel Sun 主题: Re: [VOTE] Release Groovy 2.4.9 Hi Daniel, I won't includ

Re: Indy jars does not pull indy dependencies

+User group Anyone from user group know about this? On Fri, Feb 24, 2017 at 2:37 PM, Raviteja Lokineni < raviteja.lokin...@gmail.com> wrote: > I was using groovy-templates:indy in my projects but the dependency tree > was showing non-indy dependencies. So I had to do this: > > compile 'org.codeh

Re: Grape and loading classes that extend java.lang.Exception from compiled Groovy bytecode

Tonight I got this to load the EmailException class a few times without any changes to the source - so it must be a race condition. I guess the static initializer at the bottom is a call to Grape#grab(Map dependency) with the effect of adding the commons-email JAR to the classpath. And I gue

Re: Grape and loading classes that extend java.lang.Exception from compiled Groovy bytecode

Is there a reason you don't want to use: @GrabConfig(systemClassLoader=true) along with your @Grab? On Mon, Feb 27, 2017 at 7:51 PM, Alain Stalder wrote: > Maybe someone can point me in the right direction regarding the following > issue with Grape... > > Issue in code (in words further below):

Re: Grape and loading classes that extend java.lang.Exception from compiled Groovy bytecode

I was not aware of that option, that's already better :) ... but I am not sure if it goes far enough, as follows. I have two use cases, both involving Grengine. The more immediate one is a webapp with a single Grengine instance based on a set of Groovy script files and so far it is the only web

Re: Grape and loading classes that extend java.lang.Exception from compiled Groovy bytecode

Correction: if (args.containsKey("classLoader") && args.get("classLoader") != ClassLoader.getSystemClassLoader()) { not: if (args.containsKey("classLoader") && args.get("classLoader" != ClassLoader.getSystemClassLoader())) {