Re: More inclusive naming

We can deprecate >>> and/or remove the current names later if we feel the need. Some example >>> aliases could be something like: >>> >>> tokensWhitelist => allowedTokens >>> staticStarImportsWhitelist => allowedStaticStarImports >>> importsBlacklist => prohibitedImports (or disallowedImports) >>> >>> Thoughts? >>> >>> Cheers, Paul. >>> >>> -- Graeme Rocher

Re: [VOTE] Release Apache Groovy 3.0.0

Fantastic news! +1 — Graeme Rocher > On 9 Feb 2020, at 15:53, John Wagenleitner > wrote: > >  > +1 (binding) > >> On Fri, Feb 7, 2020, 12:43 AM Paul King wrote: >> >> Dear development community, >> >> I am happy to start the VOTE thread

Re: [ANNOUNCE] Apache Groovy 3.0.0-alpha-3 released

bsite at https://groovy.apache.org/ > > Best regards, > > The Apache Groovy team. -- Graeme Rocher

Re: [ANNOUNCE] Apache Groovy 2.5.0 released

Awesome! Congrats all! — Graeme Rocher > On 30 May 2018, at 08:38, Cédric Champeau wrote: > > Congrats to anyone involved in that long awaited release! > >> Le mer. 30 mai 2018 à 08:37, Paul King a écrit : >> Dear community, >> >> The Apache Groovy team

Re: What the... static compile by default

nity and you >> should be proud of the work you are doing with Groovy. It would be a real >> shame to lose your enthusiasm and contributions to this great language and >> great ecosystem. I mean that sincerely. >> >> Let me know whatever I can do to help. >> >> Thanks for all of your great work. Well done sir! >> >> >> >> >> JSB >> -- >> Jeff Scott Brown >> OCI Partner and Principal Software Engineer >> OCI Grails Practice Lead >> >> Autism Strikes 1 in 166 >> Find The Cause ~ Find The Cure >> http://www.autismspeaks.org/ > > -- Graeme Rocher

Re: What the... static compile by default

PM, Daniel.Sun <sun...@apache.org> wrote: > Hi Cédric, > > Feel free to remove any code. > To be honest, I am really tired. > Bye Groovy community. > > Cheers, > Daniel.Sun > > > > > -- > Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html -- Graeme Rocher

Re: [VOTE] Release Apache Groovy 2.4.15

+1 > On 23 Mar 2018, at 08:04, Paul King wrote: > > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.4.15 release! This is > mainly to fix a regression in calling static methods in interfaces. We were > trying to improve the JDK9

Re: About the native-lambda branch

t; > [1] https://github.com/apache/groovy/tree/native-lambda > > > > -- > Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html -- Graeme Rocher

Re: About SmartASMifier

> Daniel.Sun >> >> >> >> >> -- >> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html > > -- Graeme Rocher

Re: New syntax explosion

a > programmers around the office into using Groovy because it is Java plus a > *few* very convenient additons. I almost want to be able to turn off some > of these additions so the compiler errors on them. > > > > Eric Milles > Lead Software Engineer > > Thomson Reuters > > Email: eric.mil...@thomsonreuters.com > > Phone: 651-848-7040 > > -- Graeme Rocher

Re: [VOTE] Release Apache Groovy 2.6.0-alpha-1

http://groovy.329449.n5.nabble.com/VOTE-Release-Apache-Groovy-2-6-0-alpha-1-tp5742698p5742703.html > Sent from the Groovy Dev mailing list archive at Nabble.com. -- Graeme Rocher

Re: [ANNOUNCE] Apache Groovy 2.4.11 released

: >>>> http://www.groovy-lang.org/download.html >>>> Jars are also available within the major binary repositories. >>>> We would like to thank all people who contributed to this release. >>>> >>>> We welcome your help and feedback. For more information on how to >>>> report problems, and to get involved, visit the project website at >>>> https://groovy.apache.org/ >>>> >>>> Best regards, >>>> >>>> The Apache Groovy team. >>> >>> -- >>> Best regards / Med venlig hilsen, >>> Søren Berg Glasius >>> >>> Hedevej 1, Gl. Rye, 8680 Ry, Denmark >>> Mobile: +45 40 44 91 88, Skype: sbglasius >>> --- Press ESC once to quit - twice to save the changes. >> >> > -- Graeme Rocher

Re: [VOTE] Release Apache Groovy 2.4.11 (take 2)

>> View this message in context: >> http://groovy.329449.n5.nabble.com/VOTE-Release-Apache-Groovy-2-4-11-take-2-tp5740212p5740221.html >> Sent from the Groovy Dev mailing list archive at Nabble.com. > > -- Graeme Rocher

Re: Towards a better compiler

ld > put everything that affects the compiler itself, and live `--classpath` for > the user space. Doing this would let tools like Gradle be much smarter about > what they can do. > > [1] https://docs.gradle.org/3.5-rc-3/release-notes.html > [2] https://issues.apache.org/jira/browse/GROOVY-8142 > [3] https://issues.apache.org/jira/browse/GROOVY-8148 > [4] https://blog.gradle.org/incremental-compiler-avoidance -- Graeme Rocher

Re: master branch has had the 'parrot' branch merged

iew this message in context: > http://groovy.329449.n5.nabble.com/master-branch-has-had-the-parrot-branch-merged-tp5739796p5739809.html > Sent from the Groovy Dev mailing list archive at Nabble.com. -- Graeme Rocher

Re: [ANNOUNCE] Apache Groovy 2.4.10 Released

gt; documentation. Please let us know if you feel this makes the install more > useful and self-contained or whether you think it has become too fat. > > For more information on how to report problems, and to get involved, > visit the project website at: https://groovy.apache.org/ > > Best regards, > > The Apache Groovy team. -- Graeme Rocher

Re: [VOTE][LAZY] Apache Groovy Roadmap - take 2

idging version of Groovy for JDK 1.7 users who can't go >> straight to the full 1.8 based version. We can decide later whether >> this branch forms the basis of a 2.6, 3.0 or no release. >> >> This is a lazy consensus vote, so I'll go ahead and create the branch >> in 72 hrs for the purposes described above unless I hear serious >> objections. >> >> Cheers, Paul. >> > -- Graeme Rocher

Re: [VOTE] Release Apache Groovy 2.4.10 (take 2)

Apache Groovy 2.4.10 >> [ ] 0 I don't have a strong opinion about this, but I assume it's ok >> [ ] -1 Do not release Apache Groovy 2.4.10 because... >> >> Here is my vote: >> >> +1 (binding) > > > > > -- > Guillaume Laforge > Apache Groovy committer & PMC Vice-President > Developer Advocate @ Google Cloud Platform > > Blog: http://glaforge.appspot.com/ > Social: @glaforge / Google+ -- Graeme Rocher

Re: Help with pitching Groovy and Grails

i% > 2BouMPw%40mail.gmail.com > <https://groups.google.com/d/msgid/grails-dev-discuss/CAJpE9rUp8B84w6Mz7k4_zw6c2EMh4W08oe%3Dsc_xsqfJi%2BouMPw%40mail.gmail.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Graeme Rocher

Re: [VOTE] Apache Groovy Roadmap

ser', in pretty old code. >> >> >> I am thinking for example of the groovy-eclipse plugin. Also we do not >> catch all exceptions thrown by antlr afaik. >> >> But maybe I overestimate the problem >> >> bye Jochen -- Graeme Rocher

Re: release process

in what > is essentially 2.x as soon as possible. > > Cheers, > Keith > > > (as a side note, any release of Groovy that would require Java 8 would be > a no-go for Gradle in short term, be it 2.x or 3.x) > > 2017-01-24 15:45 GMT+01:00 Graeme Rocher <graeme.roc...@gmail.

Re: Traits and protected properties

ed-properties-tp5738002p5738022.html > Sent from the Groovy Dev mailing list archive at Nabble.com. -- Graeme Rocher

Re: release process

ava 8 would be a > no-go for Gradle in short term, be it 2.x or 3.x) > > 2017-01-24 15:45 GMT+01:00 Graeme Rocher <graeme.roc...@gmail.com>: >> >> Understood. >> >> I still think it would be valuable to have a Parrot + Java 8 + Groovy >> 2.x releas

Re: release process

ckd...@gmx.org> wrote: > > > On 24.01.2017 14:50, Graeme Rocher wrote: >> >> Is the plan for 3.0 to break binary compatibility for existing libraries? >> >> Personally I don't think we should ever have a version that we call >> "blow everythi

Re: MavenGrapeEngine?

>>> >>> yes I think we can do that >>> >>> >>> >>> - if we want another engine: how do we manage >>> >>> dependencies? do we >>> >>> isolate them from groovy libs? >>> >>> >>> >>> >>> >>> they should be optional for the delivery and in the >>> >>> light of >>> >>> that I think depending on spring-boot-cli is an option >>> >>> >>> >>> Alternative is to implement it in groovy without maven in a >>> >>> light >>> >>> fashion, with >>> >>> >>> >>> >>> >>> https://github.com/apache/tomee/blob/master/container/openejb-loader/src/main/java/org/apache/openejb/loader/provisining/MavenResolver.java >>> >>> >>> >>> >>> >>> <https://github.com/apache/tomee/blob/master/container/openejb-loader/src/main/java/org/apache/openejb/loader/provisining/MavenResolver.java> >>> >>> and >>> >>> >>> >>> >>> >>> https://github.com/apache/tomee/blob/master/container/openejb-loader/src/main/java/org/apache/openejb/loader/provisining/HttpResolver.java >>> >>> >>> >>> >>> >>> <https://github.com/apache/tomee/blob/master/container/openejb-loader/src/main/java/org/apache/openejb/loader/provisining/HttpResolver.java> >>> >>> you can resolve most of maven artifacts. This code needs to >>> >>> be >>> >>> reworked >>> >>> on its config side cause it is specific to tomee but my point >>> >>> is >>> >>> in < >>> >>> 400 LOC you can get a maven resolver you own and therefore >>> >>> supporting >>> >>> snapshots is very doable there. >>> >>> >>> >>> >>> >>> I would prefer depending on something existing, but 400 LOC is >>> >>> not >>> >>> much and if that goes without further dependencies... well then >>> >>> we >>> >>> should consider doing that >>> >>> >>> >>> >>> >>> Agree, I only know aether (or its forks) which are far from 400 LOC >>> >>> but >>> >>> alternatives welcomed as well if they exist >>> >>> >>> >>> bye Jochen >>> >>> >>> >>> >>> >> >>> > >> >> > -- Graeme Rocher

Re: release process

t;> >> Cheers Paul. >> >> On 21 Jan 2017 5:01 AM, "Jochen Theodorou" <blackd...@gmx.org> wrote: >>> >>> On 20.01.2017 13:14, Paul King wrote: >>>> >>>> Wasn't the consensus to have parrot just in 3.0? So we could make the >>>> 2_5_X branch now? >>> >>> >>> may have missed something like a consensus I guess. But frankly I don´t >>> get why parrot should not even be optional in 2.5.x. >>> >>> bye Jochen >>> > -- Graeme Rocher

Re: [ANNOUNCE] Apache Groovy 2.4.8 released

and feedback. For more information on how to > report problems, and to get involved, visit the project website at > https://groovy.apache.org/ > > > Best regards, > > The Apache Groovy community. -- Graeme Rocher

Re: groovy git commit: Add option -lh to launch SimpleHTTPServer

abble.com/Re-groovy-git-commit-Add-option-lh-to-launch-SimpleHTTPServer-tp5737234p5737237.html > Sent from the Groovy Dev mailing list archive at Nabble.com. -- Graeme Rocher

Re: [PROPOSAL]new operator ?=

9.n5.nabble.com/PROPOSAL-new-operator-tp5736886p5736922.html > Sent from the Groovy Dev mailing list archive at Nabble.com. -- Graeme Rocher

Re: Negative relational operators for Groovy 3

gt; -- >> View this message in context: >> http://groovy.329449.n5.nabble.com/Negative-relational-operators-for-Groovy-3-tp5736809p5736882.html >> Sent from the Groovy Dev mailing list archive at Nabble.com. >> >> >> >> -- >> Guillaume Laforge >> Apache Groovy committer & PMC Vice-President >> Developer Advocate @ Google Cloud Platform >> >> Blog: http://glaforge.appspot.com/ >> Social: @glaforge / Google+ > -- Graeme Rocher

Re: Negative relational operators for Groovy 3

from Negative relational operators for Groovy 3, click here. > NAML > > > > View this message in context: Re: Negative relational operators for Groovy 3 > Sent from the Groovy Dev mailing list archive at Nabble.com. -- Graeme Rocher

Re: Proposal: Statically compileable builders

ypes. The > information you want to transport (eventually with generics) is the delegate > of course. Yes that would be a good improvement too. I'm not sure how you express that? Any suggestions Cheers > > bye Jochen > > > > > > > > > > > > > > > > > > > > > > > -- Graeme Rocher

Re: Proposal: Statically compileable builders

6 at 5:43 PM, Jochen Theodorou <blackd...@gmx.org> wrote: > > > On 04.10.2016 16:32, Graeme Rocher wrote: > [...] >> >> I would like to propose adding the ability to create builders that can >> be statically compiled by adding a capability similar to Scala's >> Dy

Re: Proposal: Statically compileable builders

gic/groovy/mapargs/MapArgumentsTest.groovy > > Might be helpful :) > > > BR, > Sergei > > On Tue, Oct 4, 2016 at 5:33 PM Graeme Rocher <graeme.roc...@gmail.com> > wrote: >> >> Closely linked to >> >> https://issues.apache.org/jira/browse/GROOVY-7956 &

Proposal: Statically compileable builders

: * Behavior of closure delegates? * invokeMethod vs methodMissing Thoughts? Cheers -- Graeme Rocher

Re: Release 2.4.8 ?

l#comment-15481100 >>>> >>>> I think this calls for a new release. >>>> >>>> What do you think? >>>> >>>> -Pascal >>>> >>>> P.S.: I am repeating myself, but I think we should also release a >>>> 2.5.0-beta (even without the macro documentation). >> >> >> >> >> -- >> Guillaume Laforge >> Apache Groovy committer & PMC Vice-President >> Developer Advocate @ Google Cloud Platform >> >> Blog: http://glaforge.appspot.com/ >> Social: @glaforge / Google+ > > -- Graeme Rocher

Re: [CONTRIBUTION]groovy-parser

-antlr4-grammar. BTW, groovy-parser requires Java 8. > > >Currently groovy-parser supports all statements, most of > expressions(except method call expression, command expression, etc.). I wish > the groovy-parser could be done before the end of this year(2016). > > >Any suggestion and help is appreciated. > > > Cheers, > > Daniel.Sun -- Graeme Rocher

Re: Automatic closure coercion and delegate

+1 this seems like a great idea. Graeme On Wed, May 18, 2016 at 9:11 AM, Jochen Theodorou wrote: On 18.05.2016 08:46, Peter Ledbrook wrote: > I'm not even sure there's a right answer to this. I guess I would expect > local variables defined outside of the closure to be