RE: Groovy 3 lambda, method reference, default methods

I guess the Groovy 3.0/3.0-- (aka 2.6) syntax elements support will be switchable in IntelliJ, anything else would make little sense to me.But we have the expert on this mailing list, who should be able to tell us... :-)mg Ursprüngliche Nachricht Von: "Daniel.Sun"

RE: Groovy 3 lambda, method reference, default methods

I guess the Groovy 3.0/3.0-- (aka 2.6) syntax elements support will be switchable in IntelliJ, anything else would make little sense to me.But we have the expert on this mailing list, who should be able to tell us... :-)mg Ursprüngliche Nachricht Von: "Daniel.Sun"

RE: Groovy 3 lambda, method reference, default methods

That's cool that it's basically a separate project. I wonder if IntelliJ itself can use the Parrot parser then to parse Groovy code, in that case it would always be guaranteed to be 100% "compatible", at least from a syntax perspective. I bet same concept could apply to code analysis tools.

RE: Groovy 3 lambda, method reference, default methods

You can write Java8 style code(e.g. lambda, method/constructor reference, etc.) when Parrot parser is enabled :-) See https://github.com/danielsun1106/groovy-parser > Is there then a major difference in language between 2.6+Parrot and 3.0? 3.0 enables Parrot parser by default, so no

RE: Groovy 3 lambda, method reference, default methods

This is major news, if the performance is comparable to Java. So with 2.6.0-alpha-3, Parrot, and JDK8+ you can use lambda expressions in static groovy and have them compiled to native lambda, or is it using closure syntax? Is there then a major difference in language between 2.6+Parrot and 3.0?

Groovy 3 lambda, method reference, default methods

I took a look at the new Groovy 3 changes at http://groovy-lang.org/releasenotes/groovy-3.0.html and noticed there is still a question as to whether or not to implement lambdas, method references, and default methods as closures and traits. Is the Groovy team still taking feedback on these

Re: parseClass always returns the same class

Please try `public Class parseClass(final GroovyCodeSource codeSource, boolean shouldCacheSource)`, see https://github.com/apache/groovy/blob/master/src/main/groovy/groovy/lang/GroovyClassLoader.java#L323 Cheers, Daniel.Sun -- Sent from:

parseClass always returns the same class

Sorry, but I'm sure I'm confused. I'm doing: groovyLoader = new GroovyClassLoader(GroovyClass.class.getClassLoader()); only once. Then when I do: groovyClass = groovyLoader.parseClass(new File("MyClass.groovy")); I get a groovyClass that I can use just fine. However, if I change

Re: Upgrade Groovy jar - can't start tomcat

Thanks for the explanation, Paul, it makes sense. Long story short: do not upgrade major libraries in bugfix releases ;) 2018-03-21 14:38 GMT+01:00 Paul King : > The ASM 6 jar has a module-info.class file that gets incorporated into our > jar via jarjar. We obviously should

Re: Upgrade Groovy jar - can't start tomcat

The ASM 6 jar has a module-info.class file that gets incorporated into our jar via jarjar. We obviously should exclude that in our build and we do. We originally only had that build fix for 2_5_X and above builds because we didn't want to bump ASM version in a point release - but that change was

Re: Vote for Groovy 3 support in IntelliJ :-)

Here is the link: https://youtrack.jetbrains.com/issue/IDEA-188050 Cheers, Daniel.Sun -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html

Re: Vote for Groovy 3 support in IntelliJ :-)

Where do we vote for this? On Wed, Mar 21, 2018 at 7:39 AM, Daniel.Sun wrote: > Total votes are up to 121 now :-) > > Cheers, > Daniel.Sun > > > > > -- > Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html >

Re: Upgrade Groovy jar - can't start tomcat

The question is why do we have a `module-info.class` file in groovy.jar. I thought we had fixed that. Or maybe in 2.4.15? 2018-03-21 13:46 GMT+01:00 Jochen Theodorou : > > > Am 21.03.2018 um 12:34 schrieb Blake McBride: > >> Thanks! Turns out, this is a known problem with

Re: Upgrade Groovy jar - can't start tomcat

Am 21.03.2018 um 12:34 schrieb Blake McBride: Thanks!  Turns out, this is a known problem with older versions of tomcat.  I don't think any changes in groovy are necessary. just in case you are somebody else wants to know more Unable to process Jar entry [module-info.class] from Jar

Re: Vote for Groovy 3 support in IntelliJ :-)

Total votes are up to 121 now :-) Cheers, Daniel.Sun -- Sent from: http://groovy.329449.n5.nabble.com/Groovy-Users-f329450.html

Re: Upgrade Groovy jar - can't start tomcat

Thanks! Turns out, this is a known problem with older versions of tomcat. I don't think any changes in groovy are necessary. Thanks again! Blake On Wed, Mar 21, 2018 at 6:31 AM, Daniel.Sun wrote: > Hi Blake, > >After asm bumped to 6.0 on 2.4 branch, we run into

Re: Upgrade Groovy jar - can't start tomcat

I fixed the problem - upgraded tomcat. Thanks! Blake On Wed, Mar 21, 2018 at 6:01 AM, Blake McBride wrote: > Greetings, > > I have been a happy user of groovy-2.3.7 for several years now on my > tomcat webapp under Java 8. I just updated groovy-2.3.7.jar to >

Upgrade Groovy jar - can't start tomcat

Greetings, I have been a happy user of groovy-2.3.7 for several years now on my tomcat webapp under Java 8. I just updated groovy-2.3.7.jar to groovy-2.4.14.jar and now I am getting the following error: [...] Mar 21, 2018 5:47:07 AM org.apache.catalina.startup.ContextConfig

Re: Groov 3.0 - nested code blocks - block/eval

I’m against breaking changes and changing core concepts for so little gain. Groovy has (x) to make x an expression. We could make that lexically scoped. Dierk sent from:mobile > Am 21.03.2018 um 01:53 schrieb MG : > > Hi Daniel, > >> On 21.03.2018 01:33, Daniel Sun