Re: [VOTE] Release Apache Groovy 4.0.17
+1 (non binding) Happy Holidays to you all Den tirs. 19. dec. 2023 kl. 03.28 skrev Paul King : > Dear development community, > > I am happy to start the VOTE thread for a Groovy 4.0.17 release! > > This release includes 8 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353979 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_17 > Tag commit id: 0bd637ff3a7bf917fe5edb907f331861c0df8a84 > > The artifacts to be voted on are located as follows (r66156). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/4.0.17/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/4.0.17/distribution > > Release artifacts are signed with a key from the following file: > https://dist.apache.org/repos/dist/release/groovy/KEYS > > Please vote on releasing this package as Apache Groovy 4.0.17. > > Reminder on ASF release approval requirements for PMC members: > http://www.apache.org/legal/release-policy.html#release-approval > Hints on validating checksums/signatures (but replace md5sum with > sha256sum): > https://www.apache.org/info/verification.html > > 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 4.0.17 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 4.0.17 because... > > Here is my vote: > > +1 (binding) > > < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > Virus-free.www.avast.com > < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > -- Med venlig hilsen, Søren Berg Glasius Hedevej 1, Gl. Rye, 8680 Ry Mobile: +45 40 44 91 88 --- Press ESC once to quit - twice to save the changes.
Re: [VOTE] Release Apache Groovy 5.0.0-alpha-4
+1 (non binding) Happy Holidays to you all Den tirs. 19. dec. 2023 kl. 02.10 skrev Paul King : > Dear development community, > > I am happy to start the VOTE thread for a Groovy 5.0.0-alpha-4 release! > > This release includes 16 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353967 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_5_0_0_ALPHA_4 > Tag commit id: 433daecc3942257fc33c159765b25bb3aa77d3ed > > The artifacts to be voted on are located as follows (r66155). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-4/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-4/distribution > > Release artifacts are signed with a key from the following file: > https://dist.apache.org/repos/dist/release/groovy/KEYS > > Please vote on releasing this package as Apache Groovy 5.0.0-alpha-4. > > Reminder on ASF release approval requirements for PMC members: > http://www.apache.org/legal/release-policy.html#release-approval > Hints on validating checksums/signatures (but replace md5sum with > sha256sum): > https://www.apache.org/info/verification.html > > 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 5.0.0-alpha-4 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 5.0.0-alpha-4 because... > > Here is my vote: > > +1 (binding) > > < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > Virus-free.www.avast.com > < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > -- Med venlig hilsen, Søren Berg Glasius Hedevej 1, Gl. Rye, 8680 Ry Mobile: +45 40 44 91 88 --- Press ESC once to quit - twice to save the changes.
Re: [VOTE] Release Apache Groovy 3.0.20
+1 (non binding) Happy Holidays to you all Den tirs. 19. dec. 2023 kl. 03.55 skrev Paul King : > Dear development community, > > I am happy to start the VOTE thread for a Groovy 3.0.20 release! > > This release includes 59 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353572 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_20 > Tag commit id: 6ad73a654d11db5abd383dde16f8587954c07dd4 > > The artifacts to be voted on are located as follows (r66157). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/3.0.20/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/3.0.20/distribution > > Release artifacts are signed with a key from the following file: > https://dist.apache.org/repos/dist/release/groovy/KEYS > > Please vote on releasing this package as Apache Groovy 3.0.20. > > Reminder on ASF release approval requirements for PMC members: > http://www.apache.org/legal/release-policy.html#release-approval > Hints on validating checksums/signatures (but replace md5sum with > sha256sum): > https://www.apache.org/info/verification.html > > 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 3.0.20 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 3.0.20 because... > > Here is my vote: > > +1 (binding) > > < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > Virus-free.www.avast.com > < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > -- Med venlig hilsen, Søren Berg Glasius Hedevej 1, Gl. Rye, 8680 Ry Mobile: +45 40 44 91 88 --- Press ESC once to quit - twice to save the changes.
Re: [VOTE] Release Apache Groovy 5.0.0-alpha-3
+1 (not binding) Den søn. 26. nov. 2023 kl. 22.55 skrev Paul King : > Dear development community, > > I am happy to start the VOTE thread for a Groovy 5.0.0-alpha-3 release! > > This release includes 47 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353636 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_5_0_0_ALPHA_3 > Tag commit id: f56e682eab977a8b4f9a5183e54443d855614b91 > > The artifacts to be voted on are located as follows (r65554). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-3/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/5.0.0-alpha-3/distribution > > Release artifacts are signed with a key from the following file: > https://dist.apache.org/repos/dist/release/groovy/KEYS > > Please vote on releasing this package as Apache Groovy 5.0.0-alpha-3. > > Reminder on ASF release approval requirements for PMC members: > http://www.apache.org/legal/release-policy.html#release-approval > Hints on validating checksums/signatures (but replace md5sum with > sha256sum): > https://www.apache.org/info/verification.html > > 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 5.0.0-alpha-3 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 5.0.0-alpha-3 because... > > Here is my vote: > > +1 (binding) > > < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > Virus-free.www.avast.com > < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > -- Med venlig hilsen, Søren Berg Glasius Hedevej 1, Gl. Rye, 8680 Ry Mobile: +45 40 44 91 88 --- Press ESC once to quit - twice to save the changes.
Re: [VOTE] Release Apache Groovy 4.0.16
+1 (not binding) Den søn. 26. nov. 2023 kl. 21.58 skrev Paul King : > Dear development community, > > I am happy to start the VOTE thread for a Groovy 4.0.16 release! > > This release includes 25 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353637 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_16 > Tag commit id: 12918f361bf20795cc2a8a1bf736a5b440146326 > > The artifacts to be voted on are located as follows (r65550). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/4.0.16/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/4.0.16/distribution > > Release artifacts are signed with a key from the following file: > https://dist.apache.org/repos/dist/release/groovy/KEYS > > Please vote on releasing this package as Apache Groovy 4.0.16. > > Reminder on ASF release approval requirements for PMC members: > http://www.apache.org/legal/release-policy.html#release-approval > Hints on validating checksums/signatures (but replace md5sum with > sha256sum): > https://www.apache.org/info/verification.html > > 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 4.0.16 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 4.0.16 because... > > Here is my vote: > > +1 (binding) > > < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > Virus-free.www.avast.com > < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > -- Med venlig hilsen, Søren Berg Glasius Hedevej 1, Gl. Rye, 8680 Ry Mobile: +45 40 44 91 88 --- Press ESC once to quit - twice to save the changes.
Re: [VOTE] Release Apache Groovy 4.0.15
+1 (not binding) Med venlig hilsen, Søren Berg Glasius Hedevej 1, Gl. Rye, 8680 Ry Mobile: +45 40 44 91 88 --- Press ESC once to quit - twice to save the changes. Den man. 11. sep. 2023 kl. 12.48 skrev Jochen Theodorou : > +1 > On 11.09.23 11:24, Paul King wrote: > > Dear development community, > > > > I am happy to start the VOTE thread for a Groovy 4.0.15 release! > > > > This release includes 12 bug fixes/improvements as outlined in the > changelog: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353571 > > > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_15 > > Tag commit id: f821c4627c197b6332e1d0e200681f3ae411df83 > > > > The artifacts to be voted on are located as follows (r63911). > > Source release: > https://dist.apache.org/repos/dist/dev/groovy/4.0.15/sources > > Convenience binaries: > > https://dist.apache.org/repos/dist/dev/groovy/4.0.15/distribution > > > > Release artifacts are signed with a key from the following file: > > https://dist.apache.org/repos/dist/release/groovy/KEYS > > > > Please vote on releasing this package as Apache Groovy 4.0.15. > > > > Reminder on ASF release approval requirements for PMC members: > > http://www.apache.org/legal/release-policy.html#release-approval > > Hints on validating checksums/signatures (but replace md5sum with > sha256sum): > > https://www.apache.org/info/verification.html > > > > 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 4.0.15 > > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > > [ ] -1 Do not release Apache Groovy 4.0.15 because... > > > > Here is my vote: > > > > +1 (binding) > > > > < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > > Virus-free.www.avast.com > > < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > >
Re: Upcoming Groovy birthday
Not a bad idea Daniel, and with all the money FoG has, it could even be financed. Med venlig hilsen, Søren Berg Glasius Hedevej 1, Gl. Rye, 8680 Ry Mobile: +45 40 44 91 88 --- Press ESC once to quit - twice to save the changes. Den ons. 28. jun. 2023 kl. 07.15 skrev Daniel Sun : > As we all know, Java has several logos. How about creating a new Groovy > logo based on the original one? > > Cheers, > Daniel Sun > > On 2023/06/27 22:36:42 Paul King wrote: > > Hi folks, > > > > In just 2 months time, Groovy turns 20. Who has some ideas on how to > > celebrate? > > > > I plan to release the first alpha for Groovy 5 by then and also write a > > "Using Groovy with JDK21" blog post, expanding on: > > > > https://groovy.apache.org/blog/groovy-sequenced-collections > > > > But these are almost business-as-usual activities, I think our 20th needs > > something a little extra special. > > > > Thoughts? > > > > Cheers, Paul. > > > > > > < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > > Virus-free.www.avast.com > > < > https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > >
Re: [VOTE] Release Apache Groovy 3.0.18
+1 (not binding) Med venlig hilsen, Søren Berg Glasius Hedevej 1, Gl. Rye, 8680 Ry Mobile: +45 40 44 91 88 --- Press ESC once to quit - twice to save the changes. Den man. 26. jun. 2023 kl. 08.51 skrev Paul King : > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 3.0.18 release! > > This release includes 34 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353078 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_18 > Tag commit id: 07d4af6e4d3e5fbed2cf67ae0058bdcf83042e7f > > The artifacts to be voted on are located as follows (r62642). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/3.0.18/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/3.0.18/distribution > > Release artifacts are signed with a key from the following file: > https://dist.apache.org/repos/dist/release/groovy/KEYS > > Please vote on releasing this package as Apache Groovy 3.0.18. > > Reminder on ASF release approval requirements for PMC members: > http://www.apache.org/legal/release-policy.html#release-approval > Hints on validating checksums/signatures (but replace md5sum with > sha256sum): > https://www.apache.org/info/verification.html > > 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 3.0.18 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 3.0.18 because... > > Here is my vote: > > +1 (binding) > > > > <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> > Virus-free.www.avast.com > <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> > <#m_4916143649572235556_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >
Re: [VOTE] Release Apache Groovy 4.0.13
+1 (not binding) Med venlig hilsen, Søren Berg Glasius Hedevej 1, Gl. Rye, 8680 Ry Mobile: +45 40 44 91 88 --- Press ESC once to quit - twice to save the changes. Den man. 26. jun. 2023 kl. 08.32 skrev Paul King : > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 4.0.13 release! > > This release includes 25 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12353213 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_13 > Tag commit id: c8eaf830d481572e1cd668b77c2fb2b444ce8f87 > > The artifacts to be voted on are located as follows (r62641). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/4.0.13/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/4.0.13/distribution > > Release artifacts are signed with a key from the following file: > https://dist.apache.org/repos/dist/release/groovy/KEYS > > Please vote on releasing this package as Apache Groovy 4.0.13. > > Reminder on ASF release approval requirements for PMC members: > http://www.apache.org/legal/release-policy.html#release-approval > Hints on validating checksums/signatures (but replace md5sum with > sha256sum): > https://www.apache.org/info/verification.html > > 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 4.0.13 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 4.0.13 because... > > Here is my vote: > > +1 (binding) > > > > <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> > Virus-free.www.avast.com > <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> > <#m_-8806616514831804336_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >
Re: [VOTE] Release Apache Groovy 3.0.16
Always in favor of bugfixes and improvements +1 (not binding) Med venlig hilsen, Søren Berg Glasius Hedevej 1, Gl. Rye, 8680 Ry Mobile: +45 40 44 91 88 --- Press ESC once to quit - twice to save the changes. Den tors. 9. mar. 2023 kl. 06.41 skrev Paul King : > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 3.0.16 release! > > This release includes 15 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12352913 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_16 > Tag commit id: b25a7fe7e5dc970df534c1f6fc3c4de0ff9966f0 > > The artifacts to be voted on are located as follows (r60497). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/3.0.16/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/3.0.16/distribution > > Release artifacts are signed with a key from the following file: > https://dist.apache.org/repos/dist/release/groovy/KEYS > > Please vote on releasing this package as Apache Groovy 3.0.16. > > Reminder on ASF release approval requirements for PMC members: > http://www.apache.org/legal/release-policy.html#release-approval > Hints on validating checksums/signatures (but replace md5sum with > sha256sum): > https://www.apache.org/info/verification.html > > 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 3.0.16 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 3.0.16 because... > > Here is my vote: > > +1 (binding) > > > > <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> > Virus-free.www.avast.com > <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> > <#m_-6470201692721657557_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >
Re: Welcome Remko Popma to the Apache Groovy PMC!
Congratulations Remko. Med venlig hilsen, Søren Berg Glasius Hedevej 1, Gl. Rye, 8680 Ry Mobile: +45 40 44 91 88 --- Press ESC once to quit - twice to save the changes. Den ons. 13. jul. 2022 kl. 08.59 skrev Paul King : > Remko Popma has been voted as an additional member to the Apache > Groovy PMC. Congratulations Remko! > > Remko has been a committer for some time, and was the main contributor > for the groovy-cli-picocli module. He is also on the PMC of Apache > Logging. > > Cheers, Paul. > On behalf of the Apache Groovy PMC. >
Re: groovy.json.JsonSulper
First off, user questions should be sent to us...@groovy.apache.org not
dev@groovy.apache.org, as the later is for the dev team to discuss the ins
and outs of Groovy, I have added us...@groovy.apache.org to continue the
conversation there
Second, I just tried your code in Groovy Console on Groovy 4.0.1/Java 8 and
it worked, so you need to provide more information about what version of
Groovy and Java you are using.
Bonus, this:
def req = new URL("https://jsonplaceholder.typicode.com/todos/1
").openConnection();
def postRC = req.getResponseCode();
def streamText = req.getInputStream().getText()
can be replaced with:
def streamText = 'https://jsonplaceholder.typicode.com/todos/1'.toURL().text
Med venlig hilsen,
Søren Berg Glasius
Hedevej 1, Gl. Rye, 8680 Ry
Mobile: +45 40 44 91 88
--- Press ESC once to quit - twice to save the changes.
Den tir. 5. jul. 2022 kl. 12.49 skrev Dharma Teja :
> Hi Team,
>
> When I was using the below groovy script, *groovy.json.JsonSulper *was
> throwing this error, Can you please help me with this
>
> Throws java.lang.RuntimeException: Unable to load FastStringService
>
>
> import groovy.json.*
> import java.net.http.*
> def req = new URL("https://jsonplaceholder.typicode.com/todos/1
> ").openConnection();
> def postRC = req.getResponseCode();
> def streamText = req.getInputStream().getText()
> def jsonSlurper = new JsonSlurper()
> println streamText
> def json = jsonSlurper.parseText(streamText)
> println json
>
>
> Thanks,
> Teja
>
Re: [VOTE] Release Apache Groovy 4.0.1
+1 (not binding) 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. Den ons. 2. mar. 2022 kl. 06.33 skrev Paul King : > Dear development community, > > I am happy to start the VOTE thread for a Groovy 4.0.1 release! > > This release includes 40 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12351284 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_1 > Tag commit id: 46976eec3670418873d69c0577ceda00b38fd754 > > The artifacts to be voted on are located as follows (r52805). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/4.0.1/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/4.0.1/distribution > > Release artifacts are signed with a key from the following file: > https://dist.apache.org/repos/dist/release/groovy/KEYS > > Please vote on releasing this package as Apache Groovy 4.0.1. > > Reminder on ASF release approval requirements for PMC members: > http://www.apache.org/legal/release-policy.html#release-approval > Hints on validating checksums/signatures (but replace md5sum with > sha256sum): > https://www.apache.org/info/verification.html > > 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 4.0.1 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 4.0.1 because... > > Here is my vote: > > +1 (binding) >
Re: [VOTE] Release Apache Groovy 3.0.10
+1 (not binding) 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. Den ons. 2. mar. 2022 kl. 05.41 skrev Paul King : > Dear development community, > > I am happy to start the VOTE thread for a Groovy 3.0.10 release! > > This release includes 93 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12350584 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_10 > Tag commit id: cde25a15c16eff4fc7f99b3c8706f5750a118305 > > The artifacts to be voted on are located as follows (r52802). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/3.0.10/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/3.0.10/distribution > > Release artifacts are signed with a key from the following file: > https://dist.apache.org/repos/dist/release/groovy/KEYS > > Please vote on releasing this package as Apache Groovy 3.0.10. > > Reminder on ASF release approval requirements for PMC members: > http://www.apache.org/legal/release-policy.html#release-approval > Hints on validating checksums/signatures (but replace md5sum with > sha256sum): > https://www.apache.org/info/verification.html > > 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 3.0.10 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 3.0.10 because... > > Here is my vote: > > +1 (binding) >
Re: [VOTE] Release Apache Groovy 2.5.16 (real version)
+1 (not binding) 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. Den ons. 2. mar. 2022 kl. 05.41 skrev Paul King : > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.5.16 release! > > This release includes 108 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12350583 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_5_16 > Tag commit id: bcf72d3fe865c971682bdcf1f0679623328afd13 > > The artifacts to be voted on are located as follows (r52804). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/2.5.16/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/2.5.16/distribution > > Release artifacts are signed with a key from the following file: > https://dist.apache.org/repos/dist/release/groovy/KEYS > > Please vote on releasing this package as Apache Groovy 2.5.16. > > Reminder on ASF release approval requirements for PMC members: > http://www.apache.org/legal/release-policy.html#release-approval > Hints on validating checksums/signatures (but replace md5sum with > sha256sum): > https://www.apache.org/info/verification.html > > 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.16 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 2.5.16 because... > > Here is my vote: > > +1 (binding) >
Re: [VOTE] Release Apache Groovy 4.0.0
+1 (not binding) Great that Groovy 4.0.0 is about to be released. Yet another milestone. 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. Den tir. 25. jan. 2022 kl. 12.49 skrev Paul King : > Dear development community, > > I am happy to start the VOTE thread for a Groovy 4.0.0 release! > > This release includes 28 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12351156 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_0 > Tag commit id: 44db8b9dc41c28b9d5acb0df2d2acefc2990e021 > > The artifacts to be voted on are located as follows (r52262). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/4.0.0/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/4.0.0/distribution > > Release artifacts are signed with a key from the following file: > https://dist.apache.org/repos/dist/release/groovy/KEYS > > Please vote on releasing this package as Apache Groovy 4.0.0. > > Reminder on ASF release approval requirements for PMC members: > http://www.apache.org/legal/release-policy.html#release-approval > Hints on validating checksums/signatures (but replace md5sum with > sha256sum): > https://www.apache.org/info/verification.html > > 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 4.0.0 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 4.0.0 because... > > Here is my vote: > > +1 (binding) >
Re: [VOTE] Release Apache Groovy 4.0.0-rc-1
+1 (not binding) 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. Den lør. 27. nov. 2021 kl. 02.13 skrev Paul King : > Dear development community, > > I am happy to start the VOTE thread for a Groovy 4.0.0-rc-1 release! > > This release includes 26 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12350848 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_0_RC_1 > Tag commit id: 2555ed859b37af21fad2621c83f89db59cbd9030 > > The artifacts to be voted on are located as follows (r51109). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/4.0.0-rc-1/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/4.0.0-rc-1/distribution > > Release artifacts are signed with a key from the following file: > https://dist.apache.org/repos/dist/release/groovy/KEYS > > Please vote on releasing this package as Apache Groovy 4.0.0-rc-1. > > Reminder on ASF release approval requirements for PMC members: > http://www.apache.org/legal/release-policy.html#release-approval > Hints on validating checksums/signatures (but replace md5sum with > sha256sum): > https://www.apache.org/info/verification.html > > 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 4.0.0-rc-1 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 4.0.0-rc-1 because... > > Here is my vote: > > +1 (binding) >
Re: A feature request: comparing LocalDate and LocalDateTime using built-in operators.
I think this is a very good idea, and give a +1 for the idea and implementation. 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. Den tir. 16. nov. 2021 kl. 15.24 skrev ssz : > > Hello everyone, > > Before creating a PR (or\and an issue in Jira) I would like to discuss a > possible feature. > > In our product we need the ability to compare `java.time.LocalDate` and > `java.time.LocalDateTime` objects easily without knowing the exact type. > For this we have historical reasons: we have a groovy-based engine and a > lot of client scripts with date comparison. > Until recently, we used a customized version of joda-time, that allows > such operations. > As practice has shown, it was very convenient. > But now for some reasons we have decided to abandon joda-time in favor of > pure java-time. > So, in order not to break anyone's scripts it would be nice for us if > groovy could support comparisons of those date-objects out of the box. > > To demonstrate what I mean here is a draft: > > > https://github.com/greendatasoft/groovy/commit/c55d722e6b6ead9d6e0123835c62a5fa4f525ffe > > Here, we represent `java.time.LocalDate` as a `java.time.LocalDateTime` at > midnight. > It seems this way can't break any code, and at the same time it would be > user-friendly. > But for those who have weird logic with exception handling, there is a > "groovy.compare.local-date-and-datetime" option, which allows to return > back the original behaviour. > > Please tell me what you think. > Can I proceed with PR? > Or maybe there is a better way to customize groovy to achieve the same > behaviour? >
Re: [VOTE] Release Apache Groovy 2.5.15
+1 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. Den fre. 3. sep. 2021 kl. 03.54 skrev Paul King : > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 2.5.15 release! > > This release includes 42 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12349466 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_5_15 > Tag commit id: 4421ab5a0c64eccac7ac6100307bd966e2c09071 > > The artifacts to be voted on are located as follows (r49730). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/2.5.15/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/2.5.15/distribution > > Release artifacts are signed with a key from the following file: > https://dist.apache.org/repos/dist/release/groovy/KEYS > > Please vote on releasing this package as Apache Groovy 2.5.15. > > Reminder on ASF release approval requirements for PMC members: > http://www.apache.org/legal/release-policy.html#release-approval > Hints on validating checksums/signatures (but replace md5sum with > sha256sum): > https://www.apache.org/info/verification.html > > 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.15 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 2.5.15 because... > > Here is my vote: > > +1 (binding) > >
Re: [VOTE] Release Apache Groovy 3.0.9
+1 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. Den fre. 3. sep. 2021 kl. 03.36 skrev Paul King : > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 3.0.9 release! > > This release includes 79 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12350100 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_9 > Tag commit id: 83a48afdc11bd01f01bb91ab12ac73d9feee0eda > > The artifacts to be voted on are located as follows (r49729). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/3.0.9/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/3.0.9/distribution > > Release artifacts are signed with a key from the following file: > https://dist.apache.org/repos/dist/release/groovy/KEYS > > Please vote on releasing this package as Apache Groovy 3.0.9. > > Reminder on ASF release approval requirements for PMC members: > http://www.apache.org/legal/release-policy.html#release-approval > Hints on validating checksums/signatures (but replace md5sum with > sha256sum): > https://www.apache.org/info/verification.html > > 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 3.0.9 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 3.0.9 because... > > Here is my vote: > > +1 (binding) > >
Re: [VOTE] Release Apache Groovy 4.0.0-beta-1
+1 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. Den fre. 3. sep. 2021 kl. 03.17 skrev Paul King : > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 4.0.0-beta-1 release! > > This release includes 136 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12350080 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_0_BETA_1 > Tag commit id: 18d2a11d2ffc8f4a93a1b99bd1d3bb7adfec5a12 > > The artifacts to be voted on are located as follows (r49728). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/4.0.0-beta-1/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/4.0.0-beta-1/distribution > > Release artifacts are signed with a key from the following file: > https://dist.apache.org/repos/dist/release/groovy/KEYS > > Please vote on releasing this package as Apache Groovy 4.0.0-beta-1. > > Reminder on ASF release approval requirements for PMC members: > http://www.apache.org/legal/release-policy.html#release-approval > Hints on validating checksums/signatures (but replace md5sum with > sha256sum): > https://www.apache.org/info/verification.html > > 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 4.0.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 4.0.0-beta-1 because... > > Here is my vote: > > +1 (binding) > >
Re: [VOTE] Release Apache Groovy 4.0.0-alpha-3
+1 Med venlig hilsen / Best regards Søren Berg Glasius Sent from my phone, thus brief On Tue, Apr 13, 2021, 04:56 Paul King wrote: > Dear development community, > > I am happy to start the VOTE thread for a Groovy 4.0.0-alpha-3 release! > > This release includes 152 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12349469 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_4_0_0_ALPHA_3 > Tag commit id: bdd219508feef5893372bf1b96ead893f2f2869b > > The artifacts to be voted on are located as follows (r47022). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/4.0.0-alpha-3/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/4.0.0-alpha-3/distribution > > Release artifacts are signed with a key from the following file: > https://dist.apache.org/repos/dist/release/groovy/KEYS > > Please vote on releasing this package as Apache Groovy 4.0.0-alpha-3. > > Reminder on ASF release approval requirements for PMC members: > http://www.apache.org/legal/release-policy.html#release-approval > Hints on validating checksums/signatures (but replace md5sum with > sha256sum): > https://www.apache.org/info/verification.html > > 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 4.0.0-alpha-3 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 4.0.0-alpha-3 because... > > Here is my vote: > > +1 (binding) > >
Re: ApacheCon 2021
I can also make myself available as my time permits. 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. Den tor. 18. feb. 2021 kl. 00.25 skrev Leo Gertsenshteyn : > I don't know how many hours I'll have to put in, all told, but I'd love to > be part of this. > > Cheers, > Leo > > On Wed, Feb 17, 2021 at 7:17 AM Guillaume Laforge > wrote: > >> I'd be happy to participate too :-) >> >> On Wed, Feb 17, 2021 at 2:38 PM Andres Almiray >> wrote: >> >>> Count me in as well! >>> >>> Sent from my primitive tricorder >>> >>> On 17 Feb 2021, at 13:30, Paul King wrote: >>> >>> >>> >>> Hi Folks, >>> >>> Very early planning for ApacheCon 2021 has started. No details as yet. I >>> have tentatively put my hand up to be involved with putting together a >>> Groovy track like we did last year. I'd be keen for any feedback and let me >>> know if you are interested in helping out. >>> >>> Cheers, Paul. >>> >>> >>> >>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> >>> Virus-free. >>> www.avast.com >>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> >>> <#m_-2138968161187847295_m_5808833200298002248_m_-5762977170031533532_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >>> >>> >> >> -- >> Guillaume Laforge >> Apache Groovy committer >> Developer Advocate @ Google Cloud Platform >> >> Blog: http://glaforge.appspot.com/ >> Twitter: @glaforge <http://twitter.com/glaforge> >> > > On Wed, Feb 17, 2021 at 7:17 AM Guillaume Laforge > wrote: > >> I'd be happy to participate too :-) >> >> On Wed, Feb 17, 2021 at 2:38 PM Andres Almiray >> wrote: >> >>> Count me in as well! >>> >>> Sent from my primitive tricorder >>> >>> On 17 Feb 2021, at 13:30, Paul King wrote: >>> >>> >>> >>> Hi Folks, >>> >>> Very early planning for ApacheCon 2021 has started. No details as yet. I >>> have tentatively put my hand up to be involved with putting together a >>> Groovy track like we did last year. I'd be keen for any feedback and let me >>> know if you are interested in helping out. >>> >>> Cheers, Paul. >>> >>> >>> >>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> >>> Virus-free. >>> www.avast.com >>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> >>> <#m_-2138968161187847295_m_5808833200298002248_m_-5762977170031533532_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >>> >>> >> >> -- >> Guillaume Laforge >> Apache Groovy committer >> Developer Advocate @ Google Cloud Platform >> >> Blog: http://glaforge.appspot.com/ >> Twitter: @glaforge <http://twitter.com/glaforge> >> >
Re: [DRAFT] Apache Groovy Board Report February 2021 (reporting on Nov/Dec/Jan)
Looks good to me :-) 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. Den tir. 9. feb. 2021 kl. 05.24 skrev Paul King : > > Hi Folks, > > Any other updates/comments before I submit our latest board report? (Due > tomorrow) > > Thanks, Paul. > > ===>8== > > ## Description: > Apache Groovy is responsible for the evolution and maintenance of the > Groovy > programming language > > ## Issues: > No issues requiring board attention at this time. > > ## Membership Data: > Apache Groovy was founded 2015-11-18 (5 years ago) > There are currently 20 committers and 11 PMC members in this project. > The Committer-to-PMC ratio is roughly 5:3. > > Community changes, past quarter: > - Eric Milles was added to the PMC on 2020-11-20 > - No new committers. Last addition was Mikko Värri on 2020-06-03. > > ## Project Activity: > We continue to work on bug fixes for 2.5 and 3 and continue to assist > other non-Apache projects within the Groovy ecosystem move to 3.0. > > We are also continuing on our roadmap for Groovy 4 and recently > released another alpha version. We expect to move to beta/RC versions > shortly with GA release expected later this year. > > Recent releases: > - 4.0.0-alpha-2 was released on 2020-12-04. > - 3.0.7 was released on 2020-12-03. > - 2.5.14 was released on 2020-12-03. > - 2.4.21 was released on 2020-12-03. > > We had 21 releases for 2020, making it a good year > stats-wise (there have been 211 releases since 2003). > > Downloads (Maven central/bintray only): > - For Nov/Dec/Jan quarter: approx 108 million > - last 12 months: ~350M > - since 2012 (when we started keeping stats from above repos): ~740M > > ## Community Health: > The overall community status remains healthy. > This quarter, 472/716 commits were contributed from 13 contributors > to master/all branches including 9 non-committer contributors (6 new). > This represents fairly normal activity for the project as does > recent mailing list and bug tracker activity. > > Apache Groovy continues to rank well on the TIOBE language > popularity index between 10th to 12th for most of the past 6 months. > There are flaws with the index and it fluctuates somewhat > but it is still nice to be not too far down the ranking. > > > > <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> > Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> > <#m_-4868885212564235344_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >
Re: code of conduct
I agree with Paul, There is no harm in having a CoC and to follow the general ASF one. I run GR8Conf, and we added a CoC for the conference, even without ever having to use it, but it's nice to have, in case someone does misbehave. It gives the organizers a tool to ask people to leave, if stepping over a line. The same goes for a CoC in an open source project like Groovy 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. Den fre. 20. nov. 2020 kl. 06.09 skrev Paul King : > I don't think anyone is suggesting we need a separate CoC. We just now > have a short para which shows the link to the ASF one: > > https://github.com/apache/groovy/blob/master/CODE_OF_CONDUCT.md > > Groovy has been very lucky to have on the whole a very friendly community. > I guess in any community you can have a wide range of views, a wide range > of views of what constitutes acceptable behavior, and a wide range of views > of what should be spelt out about civility. I see a CoC as being a line in > the sand at one end of a spectrum. My experiences in the Groovy community > is that we are at the other end of the spectrum entirely, but I don't want > to presume to speak for others who may be more sensitive. I don't think we > ever want a situation where we can't have robust discussions, but I see no > harm in being explicit that we should respect one another as we do. > > Cheers, Paul. > > > On Fri, Nov 20, 2020 at 2:21 PM Konstantin Boudnik wrote: > >> Ever since Linux Foundation started pushing the COC gags into ASF >> projects I kept wondering if people won't behave in civil manner - just >> like Paul has alluded to - unless they are explicitly told how to be >> good boys and girls? >> >> Let me ask a perhaps naive but a very honest question: why do we really >> need a COC? The ASF has some sort of it in the books already, why do we >> need a separate one? >> >> Is it because Microsoft's github requires a checkmark due to their >> virtue signaling being blown out of proportions? Or is it something else >> that I am missing? >> >> If you prefer a private reply - be my guest. I really want to know. >> Thank you! >> >> With regards, >>Cos >> >> On 18.11.2020 02:47, Paul King wrote: >> > >> > Hi everyone, >> > >> > We have been fortunate that most of the time, the discussions within >> > our community are very respectful, so I don't think we need to have an >> > elaborate discussion about a project-specific code of conduct. It seems >> > worthwhile though, pointing to the general code of conduct established >> > by the ASF[1] which I propose to do: >> > >> > https://github.com/apache/groovy/pull/1422 >> > <https://github.com/apache/groovy/pull/1422> >> > >> > Let me know if you see any possible improvements/issues. >> > >> > Thanks, Paul. >> > [1] https://www.apache.org/foundation/policies/conduct.html >> > <https://www.apache.org/foundation/policies/conduct.html> >> > >> >
Re: code of conduct
+1 for having a COC 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. Den ons. 18. nov. 2020 kl. 00.48 skrev Paul King : > > Hi everyone, > > We have been fortunate that most of the time, the discussions within > our community are very respectful, so I don't think we need to have an > elaborate discussion about a project-specific code of conduct. It seems > worthwhile though, pointing to the general code of conduct established by > the ASF[1] which I propose to do: > > https://github.com/apache/groovy/pull/1422 > > Let me know if you see any possible improvements/issues. > > Thanks, Paul. > [1] https://www.apache.org/foundation/policies/conduct.html > >
Re: More inclusive naming
+1 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. Den tor. 11. jun. 2020 kl. 16.50 skrev Paul King : > Hi folks, > > Given recent world events, there are numerous projects that are taking the > opportunity to use more inclusive terminology especially in names within > APIs. E.g. getting rid of things like master/slave, blacklist/whitelist, > etc. While I have never witnessed any racist behavior in the Groovy > community, it seems worthwhile to be as inclusive as we can. I scanned our > codebase and it seems that the only potential candidate we have for such a > change would be in SecureASTCustomizer. But feel free to chime in if you > think there are others. > > For backwards compatibility, I wouldn't propose to remove the old names in > the first instance, just provide friendly 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. > >
Re: logo permission
I have NEVER considered the Groovy logo to look like the communist star. As a matter of fact, I find the Groovy Star logo easily recognizable, and in the given case, I like it over the circled G. 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. Den ons. 20. maj 2020 kl. 21.47 skrev MG : > I have added a comment suggesting considering using the Groovy "icon"/Jira > logo instead of the communist star one ( > https://en.wikipedia.org/wiki/Red_star) G-) > Cheers, > mg > > On 20/05/2020 20:00, Carl Marcum wrote: > > I have attached the screenshots to this issue [1]. > Please let me know if you have any questions. > > [1] https://issues.apache.org/jira/browse/GROOVY-9564 > > On Wed, May 20, 2020 at 6:32 AM Carl Marcum wrote: > >> Hi Paul, >> >> Having trouble attaching the image to Jira for some reason so I'm >> getting with infra about it. >> >> I'll post back the issue when created. >> >> Thanks, >> Carl >> >> On 5/19/20 10:31 PM, Paul King wrote: >> > Hi Carl, >> > >> > This sounds like the kind of use of the Groovy logo that we'd like to >> > support. Can I ask you to create a Groovy Jira issue and attach a >> > screenshot. >> > >> > Thanks, Paul. >> > >> > >> > On Wed, May 20, 2020 at 11:40 AM Carl Marcum > > <mailto:cmar...@apache.org>> wrote: >> > >> > Hello, >> > >> > I'm wrapping up work on an Apache OpenOffice extension to add Apache >> > Groovy as a scripting language to OpenOffice. >> > >> > The extensions require a small thumbnail image that displays in the >> > Extension Manager for each installed extension beside the extension >> > title and description. >> > >> > I request to use the Groovy star logo for this thumbnail if >> > possible as >> > Groovy is the whole point of the extension. >> > >> > Although I'm on the AOO PMC this extension is a personal project >> > for the >> > time being and I plan on releasing it through our >> > extensions.openoffice.org <http://extensions.openoffice.org> site >> > under the Apache license. >> > >> > I can send a screenshot if you would like to see the intended usage. >> > I'm subscribed to dev@ or feel free to contact me directly. >> > >> > Best regards, >> > Carl Marcum >> > >> >> >
Re: [VOTE] Add a shorthand "final var" keyword
+1 I like the idea. 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. Den tir. 28. apr. 2020 kl. 14.24 skrev mojo2012 : > Dear development community, > > I'm a long time java developer and I'm used to add "final" to my variable > definition: final var name = "a" > > I think the *"var"* keyword (and the old "*def*" keyword) itself helps a > lot, but seeing "*var*" and "*final var*" not being aligned properly in > code > makes me crazy. > > As we have def and var in groovy, wouldn't it be nice to have a val or let > in groovy too, that is just a short form of "final var"? > > Although personally I would prefer "*val*" I do understand that some people > might have problems differentiating "*var*" and "*val*", hence the "*let*". > Both *Kotlin* and *Scala* went for the "val" keyword as well - so it might > not bee too bad. > > Anyway I created a JIRA ticket for this: > https://issues.apache.org/jira/browse/GROOVY-9308 > And I created a *patch PR*: https://github.com/apache/groovy/pull/1236 > > The patch as of now contains both the "let" and "val" syntax. I added tests > to check if the actual variable is final. Those tests all seem find. But I > wasn't able to see "final val" as syntax error (so the test currently > fails). > > I'm looking forward to get some feedback from you (hopefully positive :-)) > > [ ] +1 Add either val or let as new shortcut for "final def"/"final var" > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 I don't like this feature because ... > > > > > > -- > Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html >
GR8conf & JDK IO is cancelled
Hi, Just for your information Yesterday our prime minister announced that Denmark will basically shut down for the next two weeks, and our health authorities stated that the current COVID-19 virus wave is expected to continue for at least 12-16 weeks. (link <https://www.thelocal.dk/20200311/denmark-to-shut-all-schools-and-universities-to-fight-virus/amp?fbclid=IwAR0E4L9rsOG3XcTvk_XSdVfWhO730ly7C_MwIOBnqsOYX4DM-BWXXyl8-Ro> ) For this reason, the GR8Conf board has decided to cancel this years GR8Conf & JDK IO scheduled for June 2nd-4th in Copenhagen, Denmark. We will return strong in 2021, hopefully from May 26th-28th or June 2nd-4th. 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.
Re: Groovy Devcon
GR8Conf would be honored to host such conference and would gladly facilitate it with venue and catering. 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. Den tir. 3. mar. 2020 kl. 02.57 skrev Andres Almiray : > Hi Paul, > > Great idea! I’ll likely be present at Gr8conf but I’m unsure about > ApacheCon NA. > > Best > Andres > > Sent from my primitive tricorder > > > On 3 Mar 2020, at 0:29, Paul King wrote: > > > > > > > > Hi everyone, > > > > In the past, we have held various Groovydev conferences to get together > members of the core team and broader ecosystem to discuss > roadmaps/direction, and to brainstorm and hack. In the last couple of > years, we have just done some informal discussion sessions on the back of a > few conferences, but I'd like to have a more dedicated block of time if we > can arrange it. We are all busy, so I suspect the best way to make it > happen is to piggy-back on to a conference. Possible candidates are Gr8conf > EU in early June or ApacheCon NA in late September. > > If anyone could make either of those dates, let me know. > > > > Cheers, Paul. > > >
GR8Conf & JDK IO Call For Paper is open
Hi, For the past 11 years, GR8Conf has provided a high-quality conference experience for the tight-knit Apache Groovy programming language community. To expand the reach of the conference, encourage cross-pollination across the JVM, and share some of the logistical overhead, in 2020 we are joining forces with JDK IO - an annual conference run by the Danish Java user group covering technologies relevant to the entire JVM. The new, joint event GR8Conf & JDK IO will take place at the same location as in previous years, the IT University of Copenhagen, from June 2nd to 4th 2020. The conference has a global outreach, where last years edition had attendees from 25 countries world wide. You can read about our Call for Papers here: https://gr8conf.eu/cfp. If you are in a hurry here is the TL;DR version: The audience is interested in All Things Groovy and Java. Timeslots are 15 or 50 minutes, workshops three hours. Technical talks are preferred. We love code! Promotional/commercial talks will be rejected. T is covered for speakers (restrictions apply), unless of course your company can and will pay! Speakers will get a complimentary VIP conference pass and an invitation to speakers dinner. We have a Code of Conduct. You really should read the full page ;-) You can submit your talks here: https://cfp.gr8conf.org - please note, that this is an encouragement to submit a talk, not a promise that you will get a speaker slot at the conference. We are also open for sponsorships, in case your company is interested. Should that be the case, please let me know who to contact. Thank you. Thank you for your attention. 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.
Re: += and -= no longer rejected in assertion statement in Groovy 3
Hi Marcin, I think it makes sense, that it does not fail, as a +=1 returns 2 which by Groovys asBoolean is true. I am more inclined to say that Groovy 2.x had a bug, that was accepted as a compile error. Just my two cents worth. 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. Den ons. 8. jan. 2020 kl. 12.16 skrev Marcin Zajączkowski : > Hi, > > Playing with the failures which Groovy 3 brought to Spock tests itself, > I noticed that Groovy 3 no longer rejects += and -= if used in an > assertion statement: > > > def a = 1 > > assert a += 1 //passes > > assert a == 2 //passes > > While it behaves consistently, I wonder if that change it was purposely > (it was failing in Groovy 2) or the check should be enhanced: > > https://github.com/apache/groovy/commit/a17b9eb85835a5eaa306a893a0a8bcd51a49e299#diff-05fe8708ce3207739a2cb39a97426e8dR345 > ? > > Marcin > > -- > https://blog.solidsoft.info/ - Working code is not enough >
Re: Groovy Champions proposal feedback
Let me see, if I can summarize the story (from over 50 mails) There is a general +1 (14ish) right now on making a Groovy Award, and a majority of people who are in favor of the "Groovy Star" award name, both because it has a nice ring to it, because it can be associated with the Groovy logo, and because it sounds a bit like Java Rockstars. There also seems to be a general consensus that it can be given to core comitters, but also to people who contribute to frameworks/libraries in the ecosystem, and to people who in other ways (community work, conference organizers etc) makes an impact for the community. There is a discussion, wether it should be awarded as an award for a given year vs a lifetime archivement award. This is still something that needs to be agreed uppon. Besides being an honor to receive an award, it has also been suggested that there could be a monitary reward, to be regcognized by becoming a "comitter" or PMC member. If it is monitary the money could come from Friends of Groovy, if that can be agreed uppon. Awards could be announced at Groovy related conferences (GR8Conf, Greach, devnexus2gm or others) There need to be a discussion on how the nominees are appointed, and who decides on who will get the award. >From e personal point of view (and from the view of being a conference organizer) I would love to be able to hand out an award like this. But it seems that we're too late for GR8Conf at the end of this month. I hope I have captured most of the discussion bullets, other wise feel free to correct me. Have a gr8 day 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. On Wed, 8 May 2019 at 23:44, Paul King wrote: > Yes, I think that is the way to go. The Apache Groovy project recognizes > contributors to the project through making them committers and/or PMC > members. The Groovy Star awards were always proposed to be about the whole > community. That sits better with Friends-of-Groovy in my mind which also > has a whole community brief. > > Cheers, Paul. > > On Thu, May 9, 2019 at 12:55 AM Milles, Eric (TR Tech, Content & Ops) < > eric.mil...@thomsonreuters.com> wrote: > >> Can the open collective team recognize significant achievements in the >> community and make awards? You could announce one award per major >> conference (Gr8conf, Greach, Whatever2gm). >> >> -- >> *From:* Søren Berg Glasius >> *Sent:* Wednesday, May 8, 2019 9:50 AM >> *To:* dev@groovy.apache.org >> *Cc:* Jochen Theodorou >> *Subject:* Re: Groovy Champions proposal feedback >> >> How can we revive this discussion? I still think it's relevant. >> >> :) >> >> 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. >> >> >> On Fri, 2 Mar 2018 at 17:40, MG wrote: >> >> ...and, of course, the >> >> Apache Groovy Community Lifetime Achievement Award >> >> ;-) >> >> Like the name, +1 (again) on tying the award to a specific year, don't >> think that mixing commit access with the award makes sense (as in >> programming: Keep things single purpose - nobdy wants to be fat, be it >> class or human ;-) ) >> >> >> On 02.03.2018 10:11, Jochen Theodorou wrote: >> > hi all, >> > >> > I was thinking a while about all this and all the problems involved >> > here and I want to show an alternative. >> > >> > Apache Groovy Community Award >> > >> > Name surely to be changed. The idea is to give a nominal award for >> > what they did in the past. Somebody getting this award will get this >> > for a reason, which is to be stated. >> > >> > Since it is no title like "champion" and since we can give a >> > description of the reasons the award will be always specific, it is >> > not a title you carry around your lifetime and all of that. Maybe a >> > person could be awarded multiple times, but that is then to decide. >> > That means there will be no discussions about revoking the >> > championship, or for how long this is granted. Also I think the award >> > leaves better space for a good naming. Also we can give commit access >> > along with it, which may or may not be taken, but then includes the >> > official ASF way of recognizing people. >> > >> > what do you guys think? >> > >> > bye Jochen >> > >> >>
Re: Groovy Champions proposal feedback
How can we revive this discussion? I still think it's relevant. :) 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. On Fri, 2 Mar 2018 at 17:40, MG wrote: > ...and, of course, the > > Apache Groovy Community Lifetime Achievement Award > > ;-) > > Like the name, +1 (again) on tying the award to a specific year, don't > think that mixing commit access with the award makes sense (as in > programming: Keep things single purpose - nobdy wants to be fat, be it > class or human ;-) ) > > > On 02.03.2018 10:11, Jochen Theodorou wrote: > > hi all, > > > > I was thinking a while about all this and all the problems involved > > here and I want to show an alternative. > > > > Apache Groovy Community Award > > > > Name surely to be changed. The idea is to give a nominal award for > > what they did in the past. Somebody getting this award will get this > > for a reason, which is to be stated. > > > > Since it is no title like "champion" and since we can give a > > description of the reasons the award will be always specific, it is > > not a title you carry around your lifetime and all of that. Maybe a > > person could be awarded multiple times, but that is then to decide. > > That means there will be no discussions about revoking the > > championship, or for how long this is granted. Also I think the award > > leaves better space for a good naming. Also we can give commit access > > along with it, which may or may not be taken, but then includes the > > official ASF way of recognizing people. > > > > what do you guys think? > > > > bye Jochen > > > >
Re: Welcome Daniel Sun to Apache Groovy PMC
Congratulations Daniel. You help make Groovy shine! 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. On Mon, 6 May 2019 at 13:15, Paul King wrote: > > The Apache Groovy PMC has invited Daniel Sun to join the PMC and he has > accepted. You all probably know Daniel for his wonderful efforts on the > Parrot parser but he has been contributing in many other areas as well > recently. We look forward to many future contributions too! Welcome Daniel! > > Cheers, Paul. > >
GR8Conf CFP is open. Submit your Groovy talks now!
Hi Groovy Community! Happy New Year! GR8Conf has been going strong for the past 10 years, and this year will be no exception. This year the conference will take place from May 27th through 29th. and as always in Copenhagen, Denmark. See https://gr8conf.eu for more information. We are looking for talks evolving around All Things Groovy. This list is for inspiration, but proposals should not be limited to this list: - Groovy - Micronaut (also with Java and Kotlin) - Grails - Griffon - Testing (Spock etc...) - Gradle - GPars - Asciidoctor - Reactive programming using Groovy and related technologies - DevOps related talks angled with Groovy technologies - ReactJS, VueJS, Angular talks with backends in Groovy - Workshops on All Things Groovy - IoT integrated with Groovy - and many more! Proposals for talks should be made here: https://cfp.gr8conf.org before January 31st. If you have trouble logging in or if you need an extension on the deadline, please get in touch! All invited speakers will have a VIP pass for the conference (including an invitation to speakers dinner). GR8Conf can cover travel and hotel for our speakers. GR8Conf is a community driven conference, run as not-for-profit and with limited funding. We do not ask that speakers get their travel covered by their employee, but if they do, we will mention their company on our website (unless the company opt out) If your company would like to give back to the community by sponsoring our event, we have a sponsorprogram with something for all budgets. I hope to see your proposals soon! 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.
Re: [VOTE] Release Apache Groovy 3.0.0-alpha-4
+1 (not binding) Get the show on the road! :-) 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. On Thu, 27 Dec 2018 at 21:58, Paul King wrote: > > Dear development community, > > I am happy to start the VOTE thread for a Groovy 3.0.0-alpha-4 release! > This is expected to be the last "alpha" release for Groovy 3. > With 2019 upon us, it's time to put our focus on completing this next > version of Groovy! > > This release includes 139 bug fixes/improvements as outlined in the > changelog: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12343541 > > Tag: > https://gitbox.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_3_0_0_ALPHA_4 > Tag commit id: 1effb50d2e069ccfb954e525d4955d83b4a26773 > > The artifacts to be voted on are located as follows (r31693). > Source release: > https://dist.apache.org/repos/dist/dev/groovy/3.0.0-alpha-4/sources > Convenience binaries: > https://dist.apache.org/repos/dist/dev/groovy/3.0.0-alpha-4/distribution > > Release artifacts are signed with a key from the following file: > https://dist.apache.org/repos/dist/dev/groovy/KEYS > > Please vote on releasing this package as Apache Groovy 3.0.0-alpha-4. > > Reminder on ASF release approval requirements for PMC members: > http://www.apache.org/legal/release-policy.html#release-approval > Hints on validating checksums/signatures (but replace md5sum with > sha256sum): > https://www.apache.org/info/verification.html > > 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 3.0.0-alpha-4 > [ ] 0 I don't have a strong opinion about this, but I assume it's ok > [ ] -1 Do not release Apache Groovy 3.0.0-alpha-4 because... > > Here is my vote: > > +1 (binding) > >
Re: [VOTE] Release Apache Groovy 2.5.2
+1 On Mon, 13 Aug 2018 at 02:55 Eric Kinsella wrote: > +1 > > On Sun, Aug 12, 2018 at 7:17 PM, John Wagenleitner < > john.wagenleit...@gmail.com> wrote: > >> +1 (binding) >> >> >> On Fri, Aug 10, 2018 at 9:57 AM Paul King wrote: >> >>> Dear development community, >>> >>> I am happy to start the VOTE thread for a Groovy 2.5.2 release! >>> >>> This release includes 20 bug fixes/improvements as outlined in the >>> changelog: >>> >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12343651 >>> >>> Tag: >>> https://git1-us-west.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_5_2 >>> Tag commit id: 0a2c398a56f4d7431a9878550523494b73043e1d >>> >>> The artifacts to be voted on are located as follows (r28654). >>> Source release: >>> https://dist.apache.org/repos/dist/dev/groovy/2.5.2/sources >>> Convenience binaries: >>> https://dist.apache.org/repos/dist/dev/groovy/2.5.2/distribution >>> >>> Release artifacts are signed with a key from the following file: >>> https://dist.apache.org/repos/dist/dev/groovy/KEYS >>> >>> Please vote on releasing this package as Apache Groovy 2.5.2. >>> >>> Reminder on ASF release approval requirements for PMC members: >>> http://www.apache.org/legal/release-policy.html#release-approval >>> Hints on validating checksums/signatures (but replace md5sum with >>> sha256sum): >>> https://www.apache.org/info/verification.html >>> >>> 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.2 >>> [ ] 0 I don't have a strong opinion about this, but I assume it's ok >>> [ ] -1 Do not release Apache Groovy 2.5.2 because... >>> >>> Here is my vote: >>> >>> +1 (binding) >>> >>> P.S. Special thanks to Ken, Graeme and Jesper for trying out some macOS >>> fixes for me. >>> >>> >>> > -- 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.
Re: [VOTE] Release Apache Groovy 2.5.1
+1 (not binding) On Wed, 11 Jul 2018 at 12:42 Russel Winder wrote: > +1 > > > [ ] +1 Release Apache Groovy 2.5.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.1 because... > > -- > Russel. > === > Dr Russel Winder t: +44 20 7585 2200 <+44%2020%207585%202200> > 41 Buckmaster Roadm: +44 7770 465 077 <+44%207770%20465077> > London SW11 1EN, UK w: www.russel.org.uk > -- 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.
Re: [VOTE] Release Apache Groovy 2.6.0-alpha-4
+1 On Sat, 23 Jun 2018, 08.45 Andres Almiray, wrote: > Built and tested from source. > > There are 4 javadoc warnings > > > Task :javadocAll > /Users/aalmiray/Downloads/groovy-2.6.0-alpha-4/src/main/java/org/codehaus/groovy/ast/tools/GenericsUtils.java:788: > warning - Tag @link: malformed: > "#makeDeclaringAndActualGenericsTypeMap(ClassNode, ClassNode" > /Users/aalmiray/Downloads/groovy-2.6.0-alpha-4/src/main/java/org/codehaus/groovy/ast/tools/GenericsUtils.java:788: > warning - Tag @link: reference not found: > #makeDeclaringAndActualGenericsTypeMap(ClassNode, ClassNode > 2 warnings > > > Task :javadoc > /Users/aalmiray/Downloads/groovy-2.6.0-alpha-4/src/main/java/org/codehaus/groovy/ast/tools/GenericsUtils.java:788: > warning - Tag @link: malformed: > "#makeDeclaringAndActualGenericsTypeMap(ClassNode, ClassNode" > /Users/aalmiray/Downloads/groovy-2.6.0-alpha-4/src/main/java/org/codehaus/groovy/ast/tools/GenericsUtils.java:788: > warning - Tag @link: reference not found: > #makeDeclaringAndActualGenericsTypeMap(ClassNode, ClassNode > 2 warnings > > And quite the number of warnings related to asciidoc stylesheets. > > All tests passed. > > +1 (binding) > > --- > Java Champion; Groovy Enthusiast > JCP EC Associate Seat > http://andresalmiray.com > http://www.linkedin.com/in/aalmiray > -- > What goes up, must come down. Ask any system administrator. > There are 10 types of people in the world: Those who understand binary, > and those who don't. > To understand recursion, we must first understand recursion. > > On Sat, Jun 23, 2018 at 5:42 AM, Paul King wrote: > >> >> Dear development community, >> >> I am happy to start the VOTE thread for a Groovy 2.6.0-alpha-4 release! >> >> As per discussions on the user list, this is the last planned release for >> the >> GROOVY_2_6_X branch. This branch was designed as a cut-back version >> of Groovy 3.0 back-ported to run on JDK 7 but with features missing that >> required JDK 8. It was intended to help porting towards Groovy 3.0 for >> those stuck on JDK 7. This alpha version is the version to use to help >> with porting towards 3.0 if you are stuck on JDK 7. Our intention now is >> to prioritise moving towards 3.0 faster. >> >> This release includes 65 bug fixes/improvements as outlined in the >> changelog: >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123=12342855 >> >> Tag: >> https://git1-us-west.apache.org/repos/asf?p=groovy.git;a=tag;h=refs/tags/GROOVY_2_6_0_ALPHA_4 >> Tag commit id: 469016288baa219f8c04c6ecc95a082074f31901 >> >> The artifacts to be voted on are located as follows (r27680). >> Source release: >> https://dist.apache.org/repos/dist/dev/groovy/2.6.0-alpha-4/sources >> Convenience binaries: >> https://dist.apache.org/repos/dist/dev/groovy/2.6.0-alpha-4/distribution >> >> Release artifacts are signed with a key from the following file: >> https://dist.apache.org/repos/dist/dev/groovy/KEYS >> >> Please vote on releasing this package as Apache Groovy 2.6.0-alpha-4. >> >> Reminder on ASF release approval requirements for PMC members: >> http://www.apache.org/legal/release-policy.html#release-approval >> Hints on validating checksums/signatures (but replace md5sum with >> sha256sum): >> https://www.apache.org/info/verification.html >> >> 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.6.0-alpha-4 >> [ ] 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-4 because... >> >> Here is my vote: >> >> +1 (binding) >> >> > -- 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.
Last day to submit talks to GR8Conf EU 10th anniversary edition
Hi, Just want to let you know that today is the last day to propose talks for GR8Conf Europe 2018 - the 10th anniversary edition. Talks that evolves around the Groovy Ecosystem are welcomed, both beginners, intermediate and advanced talks. If you have topics that leans towards DevOps, then submit those too! You can submit at this link: http://cfp.gr8conf.org - and if you have any questions, please let me know! Best regards, Søren Berg Glasius GR8Conf Europe Organizer -- 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.
GR8Conf EU 2018 Call For Papers
Dear community, GR8Conf Europe 2018 Call For Paper is open and I would like to encourage you to submit talks to the conference. Subjects could be anything with relation to the Groovy Ecosystem, or subjects related to DevOps. You can submit your content here: http://cfp.gr8conf.org - this is your chance to shine in the Groovy community! Have a great weekend, -- 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.
Re: [VOTE] Automatic module names
+1 On Sun, 3 Dec 2017 at 18:38 Leonard Brünings <groovy-...@bruenings-it.net> wrote: > +1 with the amendment from Rémi > > Am 03.12.2017 um 11:39 schrieb Remi Forax: > > Cedric, > you can not have a dash in the name if you want the module name be > referenced in a module-info.java. > > so it should be org.apache.groovy.json > > cheers, > Rémi > > > On December 3, 2017 10:31:27 AM GMT+01:00, "Cédric Champeau" > <cedric.champ...@gmail.com> <cedric.champ...@gmail.com> wrote: >> >> Hi fellow Groovy devs, >> >> We had 2 different conversations in the past weeks regarding automatic >> module names for Groovy. We also starting receiving notifications that some >> 3rd party projects are blocked by Groovy when upgrading to modules (which >> is no surprise). Logback for one. >> >> We need to move forward, and take small steps forward. So, here's the >> plan: >> >> 1a. Replace the groovy-all jar with a groovy-all POM with just >> dependencies, so that those depending on groovy-all.jar would now get >> groovy.jar, groovy-json.jar and friends, instead of the all jar. >> 1b. Add automatic module names for all jars we have. Since we know >> breaking changes are coming, I'd suggest using "org.codehaus.groovy", >> "org.codehaus.groovy-json", ... >> 2. Fix split packages >> 3. When this is fixed, change module names to "org.apache.groovy", >> "org.apache.groovy-json", ... >> >> I would do 1a and 1b as soon as possible (2.5). >> I would do 2 and 3 for 3.0, since those are binary breaking changes. This >> is also why I would leverage that to move to org.apache module names. >> >> I am against providing another -all jar, 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, so that we can move forward. >> >> [ ] +1 The plan sounds good >> [ ] 0 I don't understand enough of the context to have an opinion >> [ ] -1 because... >> >> Thanks a lot, >> >> > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > > -- 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.
Re: float/double calculation bug ?
Hi,
This discussion does not belong on the dev mailing list, but the user
mailing list (*us...@groovy.apache.org <us...@groovy.apache.org>)*. Please
continue your very interesting discussion there :-) Thanks.
/Søren
On Sun, 19 Mar 2017 at 16:47 James Bond <sbyrne...@gmail.com> wrote:
What happens if you use .toDouble() instead of .toFloat, and an explicitly
double 100.0 literal? Right now, your computation is taking an integer,
dividing by a float, then multiplying by another float. I suspect that
going double precision won't fix this in all cases (floating point math is,
after all, just an approximation), but at least you're processing the
values as precisely as you can.
On Sun, Mar 19, 2017 at 8:28 AM, Derek Visch <derek.vi...@gmail.com> wrote:
Looks like floating point to me, what are you expecting?
On Mar 19, 2017 10:04 AM, "Tx. T" <txt8...@yahoo.com> wrote:
Any idea why the follow code "calc" returns the "70%" of the 33 incorrectly?
testing on: Groovy Version: 2.4.9 JVM: 1.8.0_112 Vendor: Oracle
Corporation OS: Mac OS X
Mac OS X 10.12.3
groovy:000> def calc = { amount, ttl ->
groovy:001> double rtn
groovy:002> if (amount[-1] != '%') rtn = amount.toDouble()
groovy:003> else rtn = ttl / 100.0 * amount.replaceAll(/%\Z/,
'').toFloat()
groovy:004>
groovy:004> rtn
groovy:005> }
===> groovysh_evaluate$_run_closure1@39fcbef6*groovy:000> calc("70%", 33)
===> 230999.997*
groovy:000> calc("10%", 33)
===> 33000.0
groovy:000> calc("20%", 33)
===> 66000.0
groovy:000> calc("30%", 33)
===> 99000.0
groovy:000> calc("40%", 33)
===> 132000.0
groovy:000> calc("50%", 33)
===> 165000.0
groovy:000> calc("60%", 33)
===> 198000.0*groovy:000> calc("70%", 33)
===> 230999.997*
groovy:000> calc("80%", 33)
===> 264000.0
groovy:000> calc("90%", 33)
===> 297000.0
groovy:000> calc("100%", 33)
===> 33.0
--
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.
Re: [VOTE] Apache Groovy Roadmap
YES (not binding). This is a clear plan, and is easy to understand for the community. It makes way for a 2.5 soon, and it also puts Parrot in a release that is not too far into the future, which IMO is important. IMO a good plan. On Tue, 31 Jan 2017 at 09:45 Cédric Champeau <cchamp...@apache.org> wrote: > YES for me too (forgot to answer :D). And yes, we should review (and > merge) your PR before beta-1. > > 2017-01-31 <20%2017%2001%2031> 9:44 GMT+01:00 Sergei Egorov < > bsid...@gmail.com>: > > YES from me. > > Would be great if we can deliver #1 as a macro method, not it form of > "MacroGroovy" (and hopefully forget this awkward name collision :D ) > > Just want to remind that there is a PR waiting for a review where I > rewrote it and implemented basic macro methods support: > https://github.com/apache/groovy/pull/472/files > > > BR, > Sergei > > On Tue, Jan 31, 2017 at 10:37 AM Cédric Champeau <cchamp...@apache.org> > wrote: > > Hi guys, > > There are multiple conversations going on for weeks, and I think they are > going nowhere. We could discuss for months what's the best plan for Groovy, > without releasing anything. Here are the challenges that are waiting for us: > > 1. release a version of Groovy that integrates Groovy macros > 2. upgrade the minimal runtime required for Groovy to 1.7, which is > required to smoothly transition to higher requirements (and also, make our > devs lives easier) > 3. upgrade the minimal runtime required for Groovy to 1.8, allowing us to > drop the old call site caching and use indy Groovy everywhere > 4. integrate Parrot, which replaces the use of Antlr2 with Antlr4 > 5. compatibility with Jigsaw, aka "Groovy as a module" > > I would like to propose the following plan: > > - Groovy 2.5: integrates 1 and 2, to be released ASAP, we've been waiting > for this for too long > - Groovy 2.6: integrate 4, implying backporting Parrot to Java 7 > - Groovy 3.0: integrate 3 and 5. The only version with necessary breaking > changes (we have no choice here) > > This plan is, I think, a good compromise for all the requirements we have: > backwards compatibility, and making progress and not having too many > branches. An alternative would be to keep Parrot on Java 8, but as some of > us have said, this is incompatible with a soonish 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. > > > -- 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.
Re: next releases
Can the parrot be packaged as separate jar that can be a dependency? That way it can be included at will On Tue, 17 Jan 2017 at 09:56 Guillaume Laforge <glafo...@gmail.com> wrote: > This is a beta, not the final release, though. > > On Tue, Jan 17, 2017 at 9:54 AM, Cédric Champeau < > cedric.champ...@gmail.com> wrote: > > I'm reluctant on adding the experimental parser in a release. It requires > a different version of antlr, which means more dependencies than we really > need. We should keep the distribution as clean as possible. Not saying that > the new parser is dirty, but that the size and dependencies of the > distribution should remain as small as possible. > > 2017-01-17 <20%2017%2001%2017> 9:48 GMT+01:00 Daniel Sun < > realblue...@hotmail.com>: > > Hi Paul, > > Will the new parser Parrot be included in 2.5.x releases as an > optional parser? 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 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> > -- 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.
Re: Negative relational operators for Groovy 3
-1 from me. Does not add pure value to the language, more like confusion. the !in and !instanceof are clear wins however. Best regards, 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. From: Guillaume Laforge <glafo...@gmail.com> <glafo...@gmail.com> Reply: dev@groovy.apache.org <dev@groovy.apache.org> <dev@groovy.apache.org> Date: 22. november 2016 at 12.44.25 To: dev@groovy.apache.org <dev@groovy.apache.org> <dev@groovy.apache.org> Cc: Groovy_Developers <d...@groovy.incubator.apache.org> <d...@groovy.incubator.apache.org> Subject: Re: Negative relational operators for Groovy 3 I must confess I'm also a bit worried with those operators too. For !in and !instanceof, I really like the idea, but here, it's closer to Ascii art. What others think? On Tue, Nov 22, 2016 at 12:35 PM, Cédric Champeau <cedric.champ...@gmail.com > wrote: > I find this very hard to decipher. The fact we wonder about the semantics > is a red warning to me. I wouldn't add those to the language. > > Le 22 nov. 2016 12:18, "Daniel Sun" <realblue...@hotmail.com> a écrit : > >> Hi Jochen, >> >> According to your proposals, I'm going to add the following >> operators: >> >> 1) !&& a !&& b === !(a && b) >> 2) !||a !|| b === !(a || b) >> 3) !& a !& b === !(a & b) >> 4) !| a !| b === !(a | b) >> 5) ~& a ~& b === ~(a & b) >> 6) ~| a ~| b === ~(a | b) >> >>Could you confirm whether the semantics of these operators are >> right >> or not? >> >> Thanks, >> Daniel.Sun >> >> >> >> -- >> 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 <http://twitter.com/glaforge> / Google+ <https://plus.google.com/u/0/114130972232398734985/posts>
Re: 2.4.7 Release?
Live releasing at GR8Conf ! ;) That's what Andres Almiray usually do. Best regards, 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. From: Cédric Champeau <cedric.champ...@gmail.com> Reply: dev@groovy.apache.org <dev@groovy.apache.org> Date: May 20, 2016 at 16:28:13 To: dev@groovy.apache.org <dev@groovy.apache.org> Subject: Re: 2.4.7 Release? That's enough for a release I would say :) 2016-05-20 16:25 GMT+02:00 Daniel Spilker <m...@daniel-spilker.com>: According to JIRA, these issues have been resolved: https://issues.apache.org/jira/issues/?jql=project%20%3D%20GROOVY%20AND%20fixVersion%20%3D%202.4.7 On Fri, May 20, 2016 at 3:25 PM, Cédric Champeau <cedric.champ...@gmail.com> wrote: A new release would be timely. Maybe we can try to get the 2.5 beta out too, would be nice for GR8Conf! What other fixes are in 2.4.7? 2016-05-20 14:34 GMT+02:00 Guillaume Laforge <glafo...@gmail.com>: I've just updated the issue. On Fri, May 20, 2016 at 2:23 PM, Daniel Spilker <m...@daniel-spilker.com> wrote: Hi Guillaume, the "Affects Version" in GROOVY-7826 is not exact. As the original reporter mentioned in a comment [1], this problem has been introduced in 2.2.0-beta-2 and I can confirm this. The commit which (indirectly) introduced the problem is 74089c1 [2]. So we would need to downgrade to 2.1.9, which would be a huge step back. OK, not compared to 1.8.9, but still... The git tag for 2.2.0-beta-2 is missing, but there is a tag named GROOVY_2_0_0_BETA_2 [3] pointing to the commit which sets the version to 2.2.0-beta-2. Can you fix that? And can you fix the "Affects Version" in JIRA? I do not have permission to edit the issue. Daniel [1]: https://issues.apache.org/jira/browse/GROOVY-7826?focusedCommentId=15270490=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15270490 [2]: https://github.com/apache/groovy/commit/74089c1156d6c296d64e68e766575e86c4119c67 [3]: https://github.com/apache/groovy/releases/tag/GROOVY_2_0_0_BETA_2 On Fri, May 20, 2016 at 11:35 AM, Guillaume Laforge <glafo...@gmail.com> wrote: Hi Daniel, No immediate plan for the moment. If GROOVY-7826 is a regression only since 2.4.5, perhaps you could migrate to 2.4.5 (considering you're migrating from the old 1.8.9) till we make a release of 2.4.7? Guillaume On Thu, May 19, 2016 at 9:01 PM, Daniel Spilker <m...@daniel-spilker.com> wrote: Hi, is there a plan to release 2.4.7 anytime soon? It's been 3 month since 2.4.6 and there have been a lot of improvements in 2.4.x. I'm asking because we updated to 2.4.6 in Jenkins 2.0 (from 1.8.9) and hit a regression with GROOVY-7826. It would be nice to have a new 2.4 release for the first Jenkins 2.x LTS release which will be cut in ~2 weeks. Regards, Daniel -- Guillaume Laforge Apache Groovy committer & PMC Vice-President Product Ninja & Advocate at Restlet Blog: http://glaforge.appspot.com/ Social: @glaforge / Google+ -- Guillaume Laforge Apache Groovy committer & PMC Vice-President Product Ninja & Advocate at Restlet Blog: http://glaforge.appspot.com/ Social: @glaforge / Google+
Re: [GitHub] groovy pull request: Link to MrHaki's blog in TupleConstructor jav...
I too agree with Cédric, that they should be in the documentation. I don't know how MrHaKi's work is licensed, but if it's open, the documentation could use his work with attributions to him. Best regards, 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. From: Guillaume Laforge <glafo...@gmail.com> Reply: dev@groovy.apache.org <dev@groovy.apache.org> Date: February 26, 2016 at 10:53:07 To: dev@groovy.apache.org <dev@groovy.apache.org> Subject: Re: [GitHub] groovy pull request: Link to MrHaki's blog in TupleConstructor jav... I agree with Cédric. It'd be better to integrate the actual tips in the JavaDocs per se. Furthermore, the Groovy's GroovyDoc can also contain code samples that are actually tested, with assertions. So not only would that improve the documentation itself, without going through another hoop to visit a website elsewhere, but it'd also would increase the number of tests, ensuring higher quality, less future regressions, etc. It's really not just a matter of clicking on a link to learn more. On Fri, Feb 26, 2016 at 10:49 AM, Cédric Champeau <cedric.champ...@gmail.com> wrote: If you're ready to introduce a link to an external resource in a Javadoc, I think you should instead make an effort to improve this particular Javadoc. I'm strongly against promoting blogs, tutorials, ... that are by nature individual rather than community driven. That, independently of the quality of the blog, or smartness of the author. We should think community first. 2016-02-26 9:22 GMT+01:00 Jesper Steen Møller <jes...@selskabet.org>: Also, people these days would usually consult documentation online sources than bother with locating any local javadoc/groovydoc documentation sources, hidden away in some local m2 repo cache (or is that just me?). That’d make a stale link somewhat less likely, outweighed by the goodness of Groovy Goodness. -Jesper On 26. feb. 2016, at 08.35, Peter Ledbrook <pe...@cacoethes.co.uk> wrote: On Wed, 24 Feb 2016 at 16:30 Cédric Champeau <cedric.champ...@gmail.com> wrote: I don't think linking to external resources like this is a good idea. We don't own the end link, it can be dead very easily, especially in the future. I would rather improve the documentation. While I understand the concern, I think this is just one of the risks of the internet. The docs already have links to the Java API docs, perhaps RFCs and other resources. Although you may have more confidence in those staying where they are, they may break in future. This is more about helping users in the short and medium term, in recognition that bulking out the javadocs themselves isn't likely to happen at a fast pace. And I'm sure it's possible to run checks over the generated javadocs to ensure that all links are valid. In fact, I'd argue that should be in place already. Then we'd have some protection against any sudden unavailability of Groovy Goodness. Peter -- Peter Ledbrook t: @pledbrook w: http://www.cacoethes.co.uk/ -- Guillaume Laforge Apache Groovy committer & PMC Vice-President Product Ninja & Advocate at Restlet Blog: http://glaforge.appspot.com/ Social: @glaforge / Google+
