Re: [VOTE] Release Apache Groovy 2.4.7

votes are cast. > > [ ] +1 Release Apache Groovy 2.4.7 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 2.4.7 > > Here is my vote: > > +1 (binding) > -- Guillaume Laforge Apache Groovy commit

Re: [20160619]Progress on the new parser for Groovy

new parser > > 5) Friendly prompt messages > > > > 6) Support lamda expression > > 7) Support do-while, the basic control structure like java's > > > > 8) Support java-like new array expression, e.g. new int[] {1, 2, 3} > > > > Finally, we want to

Re: Disable auto-assignment of jira issues?

There's about 113 issues currently assigned (if I performed the right JIRA query) On Sat, Jan 16, 2016 at 6:06 AM, Guillaume Laforge <glafo...@gmail.com> wrote: > I've moved forward and removed all component leads, and set back the > default assignment to the "default project

Re: Release 2.4.6 and 2.5.0-beta?

Let's go with it then :-) On Thu, Feb 4, 2016 at 8:57 PM, Cédric Champeau <cedric.champ...@gmail.com> wrote: > To me it looks like a bugfix, I'd be keen on backporting. > Le 4 févr. 2016 18:18, "Guillaume Laforge" <glafo...@gmail.com> a écrit : > >> Cédric,

Groovy DevCon in Copenhagen?

-- Guillaume Laforge Apache Groovy committer & PMC member Product Ninja & Advocate at Restlet <http://restlet.com> Blog: http://glaforge.appspot.com/ Social: @glaforge <http://twitter.com/glaforge> / Google+ <https://plus.google.com/u/0/114130972232398734985/posts>

Re: Antlr4-based Groovy parser status update

unary expressions. > Also, since the GSoC is a bit dated, traits are also missing. > > -Jesper -- Guillaume Laforge Apache Groovy committer & PMC Vice-President Product Ninja & Advocate at Restlet <http://restlet.com> Blog: http://glaforge.appspot.com/ Social

Re: Remove http://www.groovy-lang.org/groovy-weekly.html ?

at 8:20 AM, Pascal Schumacher <pascalschumac...@gmx.net> wrote: > Nice to hear :) > > Then we should just rename it to groovy biweekly/monthly or just groovy > newsletter. > > > Am 20.01.2016 um 00:05 schrieb Guillaume Laforge: >> >> I hope to come back to it,

Re: Preparing for a release

he/groovy/commit/fae29119a1102393ae5d1645c3fc1e06547b0ad8 > >>>> > >>>> If nobody more qualified offers his opinion on how to handle this I > >>>> would just revert, so we can release. > >>>> > >>>> Thanks, > >>>> Pascal > >>>>

Re: Release 2.5 Beta?

;> to test. Without knowing it's there and how to use it it's going to be hard >> to have feedback. >> >> 2016-03-13 0:56 GMT+01:00 Suderman Keith <suder...@cs.vassar.edu>: >> >>> >>> On Mar 12, 2016, at 12:17 PM, Guillaume Laforge <glafo...@gmail

Re: Release 2.5 Beta?

> 2016-03-13 18:18 GMT+01:00 Guillaume Laforge <glafo...@gmail.com>: > >> Aren't there any unit tests to point people to? >> >> On Sun, Mar 13, 2016 at 6:17 PM, Cédric Champeau < >> cedric.champ...@gmail.com> wrote: >> >>> The problem is how to

Re: Release 2.5 Beta?

Aren't there any unit tests to point people to? On Sun, Mar 13, 2016 at 6:17 PM, Cédric Champeau <cedric.champ...@gmail.com> wrote: > The problem is how to get feedback if the feature is not documented? > > 2016-03-13 18:13 GMT+01:00 Guillaume Laforge <glafo...@gmail.com>

Re: More Antlr4-based Groovy parser status update

are not supported without parenthesis: Try e.g. - -1 or + >-1. Is this intentional, or just an artifact of the precedence-refactored >Java grammar? > > > -Jesper > > -- Guillaume Laforge Apache Groovy committer & PMC Vice-President Product Ninja & Advocate

Re: Release 2.5 Beta?

37 Pascal Schumacher <pascalschumac...@gmx.net> >>> wrote: >>> >>>> Hello everybody, >>>> >>>> as far as I remember there was wide support for releasing a 2.5 beta in >>>> the "Release 2.4.6 and 2.5.0-beta?" discussion.

Re: http://ci.groovy-lang.org/ - "The TeamCity license will expire in 10 days."

uite easy to set up CircleCI. > > -Jesper > > > On 16. mar. 2016, at 20.04, Pascal Schumacher <pascalschumac...@gmx.net> > wrote: > > > > Hello everybody, > > > > the TeamCity license of http://ci.groovy-lang.org/ will expire soon. > > > > -

Re: http://ci.groovy-lang.org/ - "The TeamCity license will expire in 10 days."

JetBrains granted us a new license, and Cédric installed it on the server. We're good to go (or continue actually) Guillaume On Wed, Mar 16, 2016 at 10:52 PM, Guillaume Laforge <glafo...@gmail.com> wrote: > Yup, but we have a super snappy dedicated server with TeamCity that builds >

Re: Progress on the Antlr4-based parser update(2016.04.30)

Great progress guys! This is awesome and shaping up nicely! Guillaume Le 30 avr. 2016 11:27 AM, "daniel_sun" a écrit : > Hi Groovy-Dev, > > Since Jesper reported the progress last time, Jesper and I have refined > the new parser for Groovy programming language in

Re: http://www.groovy-lang.org/ down

> copy, that I replicate onto _each_ of my machines and keep up to date, but > why bother?). > > Here's hoping you make the right decision, > Steve > > On May 22, 2016, at 5:11 AM, Guillaume Laforge <glafo...@gmail.com> wrote: > > Hi Pascal, > > Yes, plea

Re: http://www.groovy-lang.org/ down

his afternoon using goDaddy and worked > flawlessly with no changed required to my internal server. So i'm a bit > puzzled why this should be a biggie  > > Sent from my iPad > > On 22 May 2016, at 20:20, Guillaume Laforge <glafo...@gmail.com> wrote: > > And... it'

Re: Problem creating groovy-macro spec files

kingBypassUsingExplicitTypeHint >> >> I've removed my examples to isolate the issue. And it turns out it just >> fails adding the testCompile dependency. Once I remove the dependency all >> tests succeed. >> >> Any ideas ? Should I've been doing the dependency ma

Re: Automatic closure coercion and delegate

> On Mon, May 2, 2016 at 10:56 AM, Guillaume Laforge <glafo...@gmail.com> > wrote: > >> +1 >> >> On Mon, May 2, 2016 at 4:44 PM, Cédric Champeau < >> cedric.champ...@gmail.com> wrote: >> >>> Hi guys, >>> >>> I've been grumpy a

Re: Helping Spread the Word about Apachecon EU 2016

p is available at > all levels. Have them contact e...@apache.org for a prospectus, and I'll > make the right introductions. > > Sponsors in the past include ... well, everyone. You have to go pretty > deep into the Forbes Technology list ( > http://fortune.com/2015/06/13/fortune-50

Re: release process

the majority for a long time shouldn't > have to wait for breaking changed to get Parrot > > Also as stupid as it is having higher version numbers will also increase > perception of maturity. > > > On Mon, 30 Jan 2017 at 23:10, Jesper Steen Møller <[hidden email]> wrote

Re: [VOTE] Apache Groovy Roadmap

] 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. > > -- Guillaume Laforge Apache Groovy committer & P

Re: About array initializer of Java style for Groovy 3

oovy.329449.n5. > nabble.com/About-array-initializer-of-Java-style-for- > Groovy-3-tp5737941p5737944.html > Sent from the Groovy Dev mailing list archive at Nabble.com. > -- Guillaume Laforge Apache Groovy committer & PMC Vice-President Developer Advocate @ Google Cloud Platfo

Re: About array initializer of Java style for Groovy 3

uot;new int[] { 2 }" for compatibility's sake. > > Sent from my iPhone > > On 24 Jan 2017, at 09:59, Daniel Sun <realblue...@hotmail.com> wrote: > > or we just support new int[] {1,2,3} ？ > > > > 在 "Guillaume Laforge [via Groovy]" <ml-node+[hidden email] &

Re: Array initializer of Java style for Groovy 3

;> >> >> Cheers, >> Daniel.Sun >> >> >> >> -- >> View this message in context: http://groovy.329449.n5.nabble >> .com/Array-initializer-of-Java-style-for-Groovy-3-tp5737955.html >> Sent from the Groovy Dev mailing list archive at Nabb

Re: release process

groovy-compat` that contains the old call site caching? >> > >> > >> > That depends. If we want to change Closure to be a functional interface >> for >> > example, then not really. groovy-compat would have to transform the code >> > using Groovy. Or we

Re: About a new annotation Groovydoc

; > > Cheers, > > Daniel.Sun > > > > > > > > -- > > View this message in context: http://groovy.329449.n5. > nabble.com/About-a-new-annotation-Groovydoc-tp5738721.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 <http://twitter.com/glaforge> / Google+ <https://plus.google.com/u/0/114130972232398734985/posts>

Re: [VOTE] Release Groovy 2.4.9

it's ok > [ ] -1 Do not release Apache Groovy 2.4.9 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>

Re: 2.4.9 release

No objection, your honor! On Thu, Feb 23, 2017 at 12:36 AM, Paul King <pa...@asert.com.au> wrote: > I am ready to release 2.4.9. Last call for any changes/fixes you want > in that release. > > Cheers, Paul. > -- Guillaume Laforge Apache Groovy committer & PMC

Re: The priority of .. and . (GROOVY-3240)

message in context: http://groovy.329449.n5. > nabble.com/The-priority-of-and-GROOVY-3240-tp5737831.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 Bl

Re: next releases

> release. > > Thoughts? > > Cheers, Paul. > -- 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>

Re: next releases

ser? If developers want to give it a try, just turn on the > switch "-Dgroovy.antlr4=true". > > Cheers, > Daniel.Sun > > > > -- > View this message in context: http://groovy.329449.n5. > nabble.com/next-releases-tp5737758p5737761.html > Sent from the Groo

Re: [VOTE] Release Groovy 2.4.9

opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 2.4.9 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>

Re: [CONTRIBUTION]groovy-parser

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. &g

Re: Release 2.4.8 ?

tabpanels:comment-tabpanel#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). >&

Re: Groovy macro documentation

> sure there must be some typos, or something that should be explained >> better... >> >> Cheers >> >> Mario >> > -- 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>

Re: [PROGRESS REPORT 20161004]groovy-parser

for developers. > > > > > > Before that I would like the parser to be able to parse the same files > and > > have no test cases failing. Because as part of the merge we need to > > integrate the parser in the test cycle to avoid any problems if we change > > the

Re: Latest documentation not showing up

Oh nice find! Thanks! On Sun, Sep 18, 2016 at 2:24 PM, Cédric Champeau <cedric.champ...@gmail.com> wrote: > Fixed. The CI build that explodes the documentation was still looking for > "groovy-docs.zip" instead of "apache-groovy-docs.zip". > > > 2016-09-18

Re: TeamCity back on track

st got the build before that successfully run our build > > and I fear that we will now have new problems. The code that uses > > setAccessible in Groovy is now pretty flexible when it comes > > setAccessible, but still... well right now we have to see for a new > > gradle fix >

Re: TeamCity back on track

Ok, thanks for confirming this. On Sun, Sep 18, 2016 at 8:18 PM, Remi Forax <fo...@univ-mlv.fr> wrote: > > > ------ > > *De: *"Guillaume Laforge" <glafo...@gmail.com> > *À: *dev@groovy.apache.org > *Envoyé: *Dimanche 18 Septembre

Re: replacing jarjar by gradle shadow plugin

Right, that's what it says on the tin: https://github.com/johnrengelman/shadow On Fri, Oct 28, 2016 at 12:01 AM, Jochen Theodorou <blackd...@gmx.org> wrote: > On 27.10.2016 21:58, Guillaume Laforge wrote: > >> Does it do package translation too? >> >

Re: Safe index for Groovy 3

Sun > > > > > > -- > View this message in context: http://groovy.329449.n5. > nabble.com/Safe-index-for-Groovy-3-tp5736558.html > Sent from the Groovy Dev mailing list archive at Nabble.com. > -- Guillaume Laforge Apache Groovy committer & PMC Vice-Presiden

Re: getting in line for the releases of groovy 2.4.8 and 2.5.0-beta-1

a of 2.5.0 out. I do not know of any criticals for >>> 2.4.x, so afaik it is ready for release any time now. For 2.5.0 I see the >>> following we should integrate the new parser (could be done for 2.4.x as >>> well), but otherwise I think we should go forward here as well. >&

Re: Lambda expression for Groovy 3

d, [1, > 2, > 3].stream().forEach(Objects::requireNonNull) > > Cheers, > Daniel.Sun > > > > -- > View this message in context: http://groovy.329449.n5. > nabble.com/Lambda-expression-for-Groovy-3-tp5736169p5736195.html > Sent from the Groovy Dev mailing list archiv

Re: Lambda expression for Groovy 3

le.view.web.template.NodeNamespace& >> breadcrumbs=notify_subscribers%21nabble%3Aemail. >> naml-instant_emails%21nabble%3Aemail.naml-send_instant_ >> email%21nabble%3Aemail.naml> >> >> >> >> >> View this message in context: Re: Lambda expression for Groovy 3 >> <http://groovy.329449.n5.nabble.com/Lambda-expression-for- >> Groovy-3-tp5736169p5736176.html> >> Sent from the Groovy Dev mailing list archive >> <http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html> at >> Nabble.com. >> > > -- 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>

Re: Lambda expression for Groovy 3

I assumed so, but wanted to be sure :-) On Tue, Oct 18, 2016 at 10:35 PM, Remi Forax <fo...@univ-mlv.fr> wrote: > I would say Groovy Closure with the Java syntax. > > Rémi > > On October 18, 2016 8:21:34 PM GMT+02:00, Guillaume Laforge < > glafo...@gmail.com> wrot

Re: Lambda expression for Groovy 3

st beta version and what feature should be included? > > Cheers, > Daniel.Sun > > > > 在 "Guillaume Laforge [via Groovy]" <ml-node+[hidden email] > <http:///user/SendEmail.jtp?type=node=5736188=0>>，2016年10月19日 > 上午7:47写道： > > Thanks for the explan

Re: Double posts

t, but I > just tried to send an e-mail to: > dev-unsubscr...@groovy.incubator.apache.org > and a received back a message from dev-h...@groovy.apache.org with > subject "confirm unsubscribe from dev@groovy.apache.org" (not the > incubator one!). > > Am I missing someth

Re: Negative relational operators for Groovy 3

Ooops, a mistake of mine with a missing parens in some code before that. We might have to pay attention to error reporting, and see how good it is to help fix developer's mistakes. On Wed, Nov 23, 2016 at 10:47 PM, Guillaume Laforge <glafo...@gmail.com> wrote: > Is the "parrot&qu

Re: [PROPOSAL]new operator ?=

less) > > On Tue, Nov 22, 2016 at 4:25 PM Guillaume Laforge <glafo...@gmail.com> > wrote: > >> It's a feature that's often be requested. >> I think Ruby's got an equivalent with ||=, and it's often the reference >> people give when exploring our Elvis operato

Re: [PROPOSAL]new operator ?=

you think about it? > > Cheers, > Daniel.Sun > > > > -- > View this message in context: http://groovy.329449.n5. > nabble.com/PROPOSAL-new-operator-tp5736886.html > Sent from the Groovy Dev mailing list archive at Nabble.com. > -- Guillaume Laforge Apache Groovy co

Re: [PROPOSAL]new operator ?=

; -- > > View this message in context: http://groovy.329449.n5. > nabble.com/PROPOSAL-new-operator-tp5736886.html > > Sent from the Groovy Dev mailing list archive at Nabble.com. > -- Guillaume Laforge Apache Groovy committer & PMC Vice-President Developer Advocate @ Google

Re: Negative relational operators for Groovy 3

wrote: > Hi all, > > The new parser(Parrot) supports negative relational operators now, > which is proposed by Guillaume Laforge :) > > Here are some example > codes(https://github.com/danielsun1106/groovy-parser/blob/ > negativeRel

Re: Negative relational operators for Groovy 3

>> >> >> In agreement with everyone else here. >>> >>> +1 to !in and !instanceof >>> -1 to everything else >>> >>> Cheers >>> >> >> even !! >> > > and then you can have > > assert a != !!a > >

Re: Negative relational operators for Groovy 3

-operators-for- >> Groovy-3-tp5736809p5736816.html >> >>> Sent from the Groovy Dev mailing list archive at Nabble.com. >> >> >> >> >> >> >> >> >> >> >> >> 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 >> > -- 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>

Re: Negative relational operators for Groovy 3

ntext: http://groovy.329449.n5.nabble.com/Negative- > relational-operators-for-Groovy-3-tp5736809p5736830.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

Re: Negative relational operators for Groovy 3

On Fri, Nov 18, 2016 at 1:58 PM, Jochen Theodorou <blackd...@gmx.org> wrote: > > > On 18.11.2016 13:45, Daniel Sun wrote: > >> Hi all, >> >> The new parser(Parrot) supports negative relational operators now, >> which is proposed by Guillaume La

Re: About the parrot branch of apache/groovy

gt; > > > -- > View this message in context: http://groovy.329449.n5. > nabble.com/About-the-parrot-branch-of-apache-groovy-tp5736722.html > Sent from the Groovy Dev mailing list archive at Nabble.com. > -- Guillaume Laforge Apache Groovy committer & PMC Vice-President Dev

Re: What Christmas gifts for us? ;)

- > > View this message in context: > > http://groovy.329449.n5.nabble.com/What-Christmas- > gifts-for-us-tp5736437.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 <http://twitter.com/glaforge> / Google+ <https://plus.google.com/u/0/114130972232398734985/posts>

Re: [PROPOSAL]Refine the implementation of LRUCache

), which is a high performance >> caching library for Java 8 and licensed under APL2. >> >> Any thoughts? >> >> Cheers, >> Daniel.Sun >> >> >> > -- Guillaume Laforge Apache Groovy committer & PMC Vice-President Developer Advocate @

Re: [PROPOSAL]Refine the implementation of LRUCache

Also it'd be nice to somehow be able to do a benchmark to see if it makes a big difference or not. On Wed, Oct 26, 2016 at 10:48 AM, Guillaume Laforge <glafo...@gmail.com> wrote: > We're careful not to add core dependencies usually, we only have ASM and > Antlr basically, but that

Re: Default Method for Groovy 3

.Sun > > > > > -- > View this message in context: http://groovy.329449.n5. > nabble.com/Default-Method-for-Groovy-3-tp5737154.html > Sent from the Groovy Dev mailing list archive at Nabble.com. > -- Guillaume Laforge Apache Groovy committer & PMC Vice-President Deve

Re: Gramma around annotations

tty much anywhere is that AST xforms could also be applied anywhere annotations are allowed. So this would open some interesting perspectives for AST transformations. -- Guillaume Laforge Apache Groovy committer & PMC Vice-President Developer Advocate @ Google Cloud Platform Blog: http://glafor

Re: [VOTE] Release Groovy 2.4.8 - take 3

tiny > in the previous attempt, I'll keep the vote open for the next 48 > hours. It 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 releas

Re: Recommended groupId for external Groovy modules

to have http-builder-ng > in Maven Central and with org.codehaus.groovy.modules is seems to be > problematic right now. > > -- > http://blog.solidsoft.info/ - Working code is not enough > -- Guillaume Laforge Apache Groovy committer & PMC Vice-President Developer Advocate @ Google Clou

Re: [VOTE] Release Apache Groovy 2.5.0-alpha-1 (take 2)

n for the next 72 hours and passes if a majority of at > least three +1 PMC votes are cast. > > [ ] +1 Release Apache Groovy 2.5.0-alpha-1 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 2.5.0-alpha-1 because... >

Re: [VOTE] Release Apache Groovy 2.5.0-alpha-1 (take 3)

465 077 xmpp: rus...@winder.org.uk > London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder -- 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>

Re: [VOTE] Release Apache Groovy 2.5.0-alpha-1 (take 2)

s package as Apache Groovy 2.5.0-alpha-1. >> >> 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.5.0-alpha-1 >> [ ] 0 I don't have a strong opinion about this, bu

Re: [VOTE] Release Apache Groovy 2.5.0-alpha-1 (take 2)

note... where can I find the current up-to-date documentation > for macros... I mean if there is one ;) > > bye Jochen > -- 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>

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

note the limitation(s). > > Paul. > > On Wed, Mar 29, 2017 at 6:13 PM, Guillaume Laforge <glafo...@gmail.com> > wrote: > > +1 (binding) > > > > I built it fine, all tests passing. > > > > I ran it as well, and things seem to work fine. > >

Re: [ANNOUNCE] Apache Groovy 2.4.10 Released

akes 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, > >

Re: Welcome John Wagenleitner to the Groovy PMC

nted stance and we welcome him as the latest member > of the Groovy PMC. Welcome John! > > Cheers, Paul. > -- Guillaume Laforge Apache Groovy committer & PMC Vice-President Developer Advocate @ Google Cloud Platform Blog: http://glaforge.appspot.com/ Social: @glaforge <http://twitter

Re: [CANCEL][VOTE] Release Apache Groovy 2.4.10

Indeed... On Tue, Mar 14, 2017 at 2:59 PM, Cédric Champeau <cedric.champ...@gmail.com> wrote: > Well, if the ASF policy allowed using the wrapper, this discussion > wouldn't happen at all. > > 2017-03-14 14:46 GMT+01:00 Guillaume Laforge <glafo...@gmail.com>: > >

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

PMC votes are cast. > > [ ] +1 Release 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 committ

Re: [VOTE] Release Apache Groovy 2.4.10

t;> >> +1 >> >> Thank you Groovy team for your efforts. >> >> -- >> Bahman Movaqar >> >> http://BahmanM.com - https://twitter.com/bahman__m >> https://github.com/bahmanm - https://gist.github.com/bahmanm >> PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) &g

Re: About LINQ-like DSL for Groovy

> > > > -- > View this message in context: http://groovy.329449.n5. > nabble.com/About-LINQ-like-DSL-for-Groovy-tp5742132p5742135.html > Sent from the Groovy Dev mailing list archive at Nabble.com. > -- Guillaume Laforge Apache Groovy committer & PMC Vice-Presid

Re: About LINQ-like DSL for Groovy

I did something similar in the Gaelyk DSL for accessing the datastore. Our command chain expressions make things pretty readable and SQL like. Now it would be good to also see how it looks like for non trivial examples, like complex where clauses, sub-queries and the like. Le 16 juil. 2017 4:02

Re: moving the Groovy website

his is just a heads-up for anyone planning to >> make changes to the site for the next little while. Probably best to >> pre-announce any such changes and I can give advice as to which repo(s) you >> should target. We might need to make changes in two places for a very short

Re: moving the Groovy website

Yeah, true. On Wed, Apr 26, 2017 at 12:51 AM, Paul King <pa...@asert.com.au> wrote: > The history will still be there in the old repo - just not as easily > accessible in the new repo if we do a clean slate approach. > > On Wed, Apr 26, 2017 at 8:43 AM, Guillaume Laforge &

Re: [VOTE] Release Apache Groovy 2.4.11

g/repos/dist/dev/groovy/KEYS > >> > >> Please vote on releasing this package as Apache Groovy 2.4.11. > >> > >> The vote is open for the next 72 hours and passes if a majority of at > >> least three +1 PMC votes are cast. > >> > >> [ ] +1

Re: apache/groovy on GitHub is empty?

e.org/repos/asf/ > > Thanks, > Roman. > > On Fri, Apr 28, 2017 at 8:50 AM, Guillaume Laforge <glafo...@gmail.com> > wrote: > > Hi Daniel, > > > > Looking at other apache/* repositories, it seems we're not the sole ones > > affected by this. > >

Re: Mini roadmap

so I won't be > able to include everything). > > Cheers, Paul. > > [1] http://thread.gmane.org/gmane.comp.lang.groovy.devel/29273 > [2] https://web.archive.org/web/20150102193203/http:// > groovy.codehaus.org/Roadmap > -- Guillaume Laforge Apache Groovy committer &am

Re: [VOTE] Release Apache Groovy 2.4.12

; 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.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 be

Re: Groovy 2.5.0-beta-1 release

n for the next 72 hours and passes if a majority of at >> least three +1 PMC votes are cast. >> >> [ ] +1 Release Apache Groovy 2.5.0-beta-1 >> [ ] 0 I don't have a strong opinion about this, but I assume it's ok >> [ ] -1 Do not release Apache Groovy 2.5.0-beta-1 becaus

Re: [2/2] groovy git commit: Refine the grammar: 1)`def` is still required for performance when declaring tuple; 2)Stop supporting command expression in parentheses

DSL is a key use case, so let's not reduce groovy's capabilities in this area, indeed. Le 16 sept. 2017 04:23, "Paul King" a écrit : > I think this is worthy of further discussion on the mailing list. I know > it's a parrot only feature so far but supporting > command

Re: [2/2] groovy git commit: Refine the grammar: 1)`def` is still required for performance when declaring tuple; 2)Stop supporting command expression in parentheses

.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 <http://twitter.com/gla

Re: [VOTE] Release Apache Groovy 2.5.0-beta-2

gt; > Cheers, > 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 <ht

Re: Groovy using Graal

0 7585 2200 voip: > sip:russel.win...@ekiga.net > 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk > London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder -- Guillaume Laforge Apache Groovy committer & PMC Vice-President Developer Advocate

Re: [Help] Need help with nabble setup

atter. - Can > anyone provide us some instruction how to do this ? > > We will be very appreciated! > > All the best, > > Piotr > -- Guillaume Laforge Apache Groovy committer & PMC Vice-President Developer Advocate @ Google Cloud Platform Blog: http://glaforge.appspot.co

Re: [VOTE] Release Apache Groovy 2.6.0-alpha-1 (take 2)

iel.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 <http://twitt

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

But apart from this build-from-source issue, if I change the version of the plugin I mentioned below, then I can successfully build the project and run things like the Groovy console. Guillaume On Mon, Nov 13, 2017 at 9:58 AM, Guillaume Laforge <glafo...@gmail.com> wrote: > Hi, > &g

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

ugguest > we should clarify the requirement of gradle version, which must be 3.5.1 to > generate the wrapper and build Apache Groovy from source. > >At last, I want to know, your vote is ? ;-) > > > Cheers, > Daniel.Sun > > > > -- > Sent from: http://groo

Re: [VOTE] Release Groovy 2.4.13

1 PMC votes are cast. >> >> [ ] +1 Release Apache Groovy 2.4.13 >> [ ] 0 I don't have a strong opinion about this, but I assume it's ok >> [ ] -1 Do not release Apache Groovy 2.4.13 because... >> >> Here is my vote: >> >> +1 (binding) >> >> P.S.

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

have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 2.4.13 because... > > Here is my vote: > > +1 (binding) > -- Guillaume Laforge Apache Groovy committer & PMC Vice-President Developer Advocate @ Google Cloud Platform Blog:

Re: [VOTE] Release Apache Groovy 2.4.13 (take 3)

abble.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 <http://twitter.com/glaforge> / Google+ <https://plus.google.com/u/0/114130972232398734985/posts>

Re: [VOTE] Automatic module names

r, which would be confusing. Also >> we have to get rid, as a larger community (java), of the bad habit of using >> fat jars as dependencies. Those should only be used in final applications, >> not libraries, so should be transparent to consumers. >> >> Please vote

Re: [DRAFT] Proposed board report for Apache Groovy for May 2018

- 2.4.15 was released on Tue Mar 27 2018 > - 2.5.0-beta-3 was released on Fri Feb 23 2018 > - 2.5.0-rc-1 was released on Mon Apr 09 2018 > - 2.6.0-alpha-3 was released on Tue Mar 06 2018 > - 3.0.0-alpha-2 was released on Tue Apr 17 2018 > > ## Mailing list activity: > > -

Re: [VOTE] Support Java-like array

array-tt5749923.html >>> ) >>> 4 votes in total(not including my +1) >>> 3 +1, >>> 10, >>> 0 -1 >>> >>> The vote is open for the next 72 hours and passes if a majority of at >>> least >>> three +1 PMC votes are cast. >>> >>> [ ] +1 Support Java-like array >>> [ ] 0 I don't have a strong opinion about this, but I assume it's ok >>> [ ] -1 Do not support Java-like array because... >>> >>> Here is my vote: >>> >>> +1 >>> >>> Cheers, >>> Daniel.Sun >>> [1] http://groovy-lang.org/differences.html >>> [2] https://github.com/apache/groovy/pull/691 >>> [3] https://issues.apache.org/jira/browse/GROOVY-8561 >>> [4] https://twitter.com/daniel_sun/status/990544485196091395 >>> >>> >>> >>> >>> >>> -- >>> 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/ Twitter: @glaforge <http://twitter.com/glaforge>

Re: [VOTE] Release Apache Groovy 2.5.0-rc-3

+1 Le dim. 20 mai 2018 à 18:30, Daniel.Sun a écrit : > "GROOVY-6167" should be finally fixed by > 1) fix resolving [1] (pushed just now, will be included in 2.5.0 GA) > 2) fix type inference [2] > > But it's really weird, I still don't know the reason why the test[3] always >

  1   2   3   4   >