Hi all,
I would like to request to become a committer again. I anticipate contributing
frequently to Groovy’s JSON support ( I have already sent half a dozen or so
pull requests ).
As for my credentials, I was previously a committer prior to the transition to
Apache and have made numerous cont
Please could my pull requests be merged before 2.4.6?
> On 10 Dec 2015, at 19:29, Pascal Schumacher wrote:
>
> Thanks. :)
>
> Are there any news regarding this?
>
> Thanks,
> Pascal
>
> Am 28.11.2015 um 16:59 schrieb Cédric Champeau:
>> +1. Last time we did the release during S2GX, and we de
FWIW these are non-breaking additions that I would appreciate going into 2.4.6
as 2.5.x might not be out for a while.
Currently I’m maintaining a temporary fork until 2.4.6 (or whatever release
includes my commits) is out
https://github.com/grails/grails-views/blob/master/json/src/main/groovy/g
y/pull/203>
>
> On Thu, Dec 10, 2015 at 1:05 PM, Graeme Rocher <mailto:graeme.roc...@gmail.com>> wrote:
> FWIW these are non-breaking additions that I would appreciate going into
> 2.4.6 as 2.5.x might not be out for a while.
>
> Currently I’m maintaining a temporary
Bit late, but +1 from me too.
Graeme
> On 22 Feb 2016, at 07:37, Paul King wrote:
>
> +1
>
> On Sun, Feb 21, 2016 at 10:25 PM, Pascal Schumacher
> wrote:
>> Hi Konstantin,
>>
>> thanks for the in-depth check. :)
>>
>> Am 19.02.2016 um 08:49 schrieb Konstantin Boudnik:
>>>
>>> - gradle.prop
+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 accessible within
> it. Wou
Please make sure to merge https://github.com/apache/groovy/pull/340 prior
to the 2.4.7 release
Thank you
Graeme
On 28 May 2016 at 13:13:47, Pascal Schumacher (pascalschumac...@gmx.net)
wrote:
+1000 to both a 2.4.7 and a 2.5-Beta release
Am 20.05.2016 um 15:25 schrieb Cédric Champeau:
A new re
>
>
>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
Hi all,
The jenkins build seems to be disabled and the Travis build is failing for
a reason that doesn’t make sense to me for pull requests
https://travis-ci.org/apache/groovy/jobs/158412284
The TeamCity builds seem to be running but doesn't handle pull requests:
http://ci.groovy-lang.org/?gues
pull requests, for security reasons. I'm not sure
why the Travis build failed with such an error...
2016-09-08 14:37 GMT+02:00 Graeme Rocher :
> Hi all,
>
> The jenkins build seems to be disabled and the Travis build is failing for
> a reason that doesn’t make sense to me for p
;>
>>>> 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
Strings (property names)
* Values have to type checked
Thoughts?
--
Graeme Rocher
tions:
* Behavior of closure delegates?
* invokeMethod vs methodMissing
Thoughts?
Cheers
--
Graeme Rocher
sTest.groovy
>
> Might be helpful :)
>
>
> BR,
> Sergei
>
> On Tue, Oct 4, 2016 at 5:33 PM Graeme Rocher
> wrote:
>>
>> Closely linked to
>>
>> https://issues.apache.org/jira/browse/GROOVY-7956
>>
>> I would like to propose adding the ability t
Oct 4, 2016 at 5:43 PM, Jochen Theodorou 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
>> Dynamic:
>
this change helps that
Cheers,
On Tue, Oct 4, 2016 at 10:35 PM, Jochen Theodorou wrote:
> On 04.10.2016 18:00, Graeme Rocher wrote:
>>
>> [...] If you combine this
>> will my other proposal around allowing delegates to on maps you can
>> see that you could impleme
On Wed, Oct 5, 2016 at 7:33 PM, Jochen Theodorou wrote:
> On 05.10.2016 08:13, Graeme Rocher wrote:
> [...]
>>
>> So again let's revisit the benefits of this change:
>>
>> 1) You can write classes annotated with @CompileStatic and use
>> builders withou
would work for both today is to
define a regular methodMissing:
def methodMissing(String name, args)
So those are some more ideas :)
Cheers
On Wed, Oct 5, 2016 at 11:25 PM, Jochen Theodorou wrote:
> On 05.10.2016 21:41, Graeme Rocher wrote:
> [...]
>>>
>>> Then for (2)
; 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
Groovy Dev mailing list archive at Nabble.com.
--
Graeme Rocher
ss.internal.worker.WorkerProcessException: Failed to run
> Gradle Compiler Daemon
> https://github.com/danielsun1106/groovy/issues/4
>
>
>Graeme, did you encounter some similiar problem like the above ever?
>
> Thanks,
> Daniel.Sun
> ___
because streams and lambda expression are
> used.
>
>
> Cheers,
> Daniel.Sun
>
> ____
> 发件人: Graeme Rocher-2 [via Groovy]
> 发送时间: 2016年10月6日 18:27
> 收件人: daniel_sun
> 主题: Re: 答复: [PROGRESS REPORT 20161004]groovy-parser
>
> Hi Daniel,
&g
> If you reply to this email, your message will be added to the discussion
> below:
> http://groovy.329449.n5.nabble.com/Negative-relational-operators-for-Groovy-3-tp5736809p5736817.html
> To unsubscribe 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
elational-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
-new-operator-tp5736886p5736922.html
> Sent from the Groovy Dev mailing list archive at Nabble.com.
--
Graeme Rocher
, which
>>> are going to make appearance in Apache Groovy 2.5. He is a very talented
>>> developer with the skills we need to help Groovy move forward.
>>>
>>> A warm welcome, and congratulations, to Sergei!
>>>
>>> Sergei, would you mind telling a few words about you?
>>>
>>> On behalf of the Apache Groovy team
>>> Cédric
>>>
>>
--
Graeme Rocher
n-lh-to-launch-SimpleHTTPServer-tp5737234p5737237.html
> Sent from the Groovy Dev mailing list archive at Nabble.com.
--
Graeme Rocher
here still
ambiguity issues?
Cheers
--
Graeme Rocher
>>
>> Please vote on releasing this package as Apache Groovy 2.4.8.
>>
>> The vote is open for the next 72 hours and passes if a majority of at
>> least three +1 PMC votes are cast.
>>
>> [ ] +1 Release Apache Groovy 2.4.8
>> [ ] 0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 2.4.8 because...
>>
>> Here is my vote:
>>
>> +1 (binding)
>
>
--
Graeme Rocher
. 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
gt;>
>> On 21 Jan 2017 5:01 AM, "Jochen Theodorou" 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
> - 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
d for years to come IMO.
Cheers
On Tue, Jan 24, 2017 at 2:55 PM, Cédric Champeau
wrote:
>
>
> 2017-01-24 14:50 GMT+01:00 Graeme Rocher :
>>
>> Is the plan for 3.0 to break binary compatibility for existing libraries?
>>
>> Personally I don't think we shoul
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 everything up version" that w
dle in short term, be it 2.x or 3.x)
>
> 2017-01-24 15:45 GMT+01:00 Graeme Rocher :
>>
>> Understood.
>>
>> I still think it would be valuable to have a Parrot + Java 8 + Groovy
>> 2.x release before Groovy 3.x
>>
>> Maybe I am alone here, but it se
5738022.html
> Sent from the Groovy Dev mailing list archive at Nabble.com.
--
Graeme Rocher
a 1.7 -> Java 1.8 a breaking change and should not
> be done in a 2.x release. This roadmap would clearly separate upgrades and
> breaking changes while still allowing people to start using Parrot in what
> is essentially 2.x as soon as possible.
>
> Cheers,
> Keith
>
>
t;>
>> 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
oonish release. The drawback is
> that Parrot has the risk of being a breaking change (it is, typically if
> people implicitly depend on the old parser, which would be bad), so there's
> a risk of not following semantic versioning.
>
> - [ ] YES, I approve the roadmap above
> - [ ] NO, I do not approve the roadmap abobe beause...
> - [ ] I don't mind, or this goes beyond what I can think of
>
> This vote is open for 72h, ending 9:30am CET, on Feb 3rd, 2017.
>
>
--
Graeme Rocher
3Dsc_xsqfJi%
> 2BouMPw%40mail.gmail.com
> <https://groups.google.com/d/msgid/grails-dev-discuss/CAJpE9rUp8B84w6Mz7k4_zw6c2EMh4W08oe%3Dsc_xsqfJi%2BouMPw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
Graeme Rocher
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
on 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
; 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
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
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
The vote is open for the next 72 hours and passes if a majority of at
>> least three +1 PMC votes are cast.
>>
>> [ ] +1 Release Apache Groovy 2.4.11
>> [ ] 0 I don't have a strong opinion about this, but I assume it's ok
>> [ ] -1 Do not release Apache Groovy 2.4.11 because...
>>
>> Here is my vote:
>>
>> +1 (binding)
>>
>
--
Graeme Rocher
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
ble 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
tes are cast.
>>>
>>> [ ] +1 Release Apache Groovy 2.4.12
>>> [ ] 0 I don't have a strong opinion about this, but I assume it's ok
>>> [ ] -1 Do not release Apache Groovy 2.4.12 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 <http://twitter.com/glaforge> / Google+
> <https://plus.google.com/u/0/114130972232398734985/posts>
>
--
Graeme Rocher
om/VOTE-Release-Apache-Groovy-2-6-0-alpha-1-tp5742698p5742703.html
> Sent from the Groovy Dev mailing list archive at Nabble.com.
--
Graeme Rocher
ng it difficult to entice fellow Java
> 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
0 I don't have a strong opinion about this, but I assume it's ok
> [ ] -1 Do not release Apache Groovy 2.6.0-alpha-2 because...
>
> Here is my vote:
>
> +1 (binding)
>
>
>
>
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
--
Graeme Rocher
heers,
>> Daniel.Sun
>>
>>
>>
>> --
>> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
>
>
>
>
> --
> Guillaume Laforge
> Apache Groovy committer & PMC Vice-President
> Developer Advocate @ Google Cloud Platform
>
> Blog: http://glaforge.appspot.com/
> Social: @glaforge / Google+
--
Graeme Rocher
ative lambda. In order to view the ASM source code(or bytecode) easily, I
>> developed a tool named SmartASMifier(
>> https://github.com/danielsun1106/SmartASMifier ). Now I share it with you
>> :-)
>>
>> Cheers,
>> Daniel.Sun
>>
>>
>>
>>
>> --
>> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
>
>
--
Graeme Rocher
m/apache/groovy/tree/native-lambda
>
>
>
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
--
Graeme Rocher
+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 experience but on the 2.4
4:59 PM, Daniel.Sun 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
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
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
project website at https://groovy.apache.org/
>
> Best regards,
>
> The Apache Groovy team.
--
Graeme Rocher
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
y aliases. 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
they will "graduate" and become their own top-level project.
> >>
> >> Further details are in the proposal:
> >>
> >> https://groovy.apache.org/wiki/grails-proposal.html
> >>
> >> Voting will be open for at least 72 hours.
> >>
> >> [ ] +1
> >> [ ] 0
> >> [ ] -1 because ...
> >>
> >> Cheers, Paul.
> >> P.S. Here is my vote:
> >> +1 paulk
>
--
Graeme Rocher
r build instructions
>> in README.md, and plan do so in the next release. Finally, there are 2
>> known groovy issues that prevent the build from being fully reproducible.
>> For the differing artifacts, we have compared the decompiled classes to
>> ensure they are as we expect to meet the ASF security team's requirements.
>> >
>> >
>> > The vote for this release is open for the next 72 hours.
>> >
>> >
>> > [ ] +1 Release Apache Grails (incubating) 7.0.0-M4
>> >
>> > [ ] 0 I don't have a strong opinion about this, but I assume it's ok
>> >
>> > [ ] -1 Do not release Apache Grails (incubating) 7.0.0-M4 because...
>> >
>> >
>> > Regards,
>> >
>> > James
>>
>
>
> --
> *Guillaume Laforge*
> Apache Groovy committer
> Developer Advocate @ Google Cloud <https://cloud.google.com/>
>
>- Blog: glaforge.dev
>- X: @glaforge <http://twitter.com/glaforge>
>- Bluesky: @glaforge.dev <https://bsky.app/profile/glaforge.dev>
>- Mastodon: @glafo...@uwyn.net <http://%40glafo...@uwyn.net/>
>
>
--
Graeme Rocher
Congrats!
Graeme Rocher
On Thu, 12 Jun 2025 at 07:04, Gianluca Sartori wrote:
> 🎉🎉🎉
>
>
> Gianluca Sartori
> --
> https://dueuno.com
>
>
> On Thu, 12 Jun 2025 at 02:36, James Daugherty
> wrote:
>
>> The Apache Grails (incubating) community is pleas
65 matches
Mail list logo
