Re: Result, was [VOTE] Groovy chairman election...

Congrats to Guillaume with my belated +1 (my excuse: I was on 2 weeks of vacation being completely unplugged in Cyprus). Thanks, Roman. On Fri, Oct 16, 2015 at 11:34 AM, Emmanuel Lécharny wrote: > Hi guys, > > here is the result for this vote : > > Guillaume Laforge got 10 +1 from : > > Cedric,

Re: Buildserver Github Pull Request Integration (Enabling Travis CI)

I have set up some builds on Jenkins including PR builds but as you noted earlier, the builds were failing. I didn't have time to investigate further. On Tue, Oct 20, 2015 at 5:01 AM, Andrew Bayer wrote: > If you need anything installed or configured, just let me know and I can > make it so. > >

Joint build exception

Dear all, I'm getting a strange exception for both 2.3.X and 2.4.X Groovy joint builds for the nextflow proje

Re: GROOVY-7635: We should consider upgrading log4j2Version on master to 2.4.1

On Mon, 2015-10-19 at 20:36 +0200, Pascal Schumacher wrote: > As far as I know we still are. I personally would prefer dropping > support for Java 6. Given the general Java-verse, I think there is no problem is saying that for future versions of Groovy JDK7 is required. -- Russel. =

Re: Buildserver Github Pull Request Integration (Enabling Travis CI)

If you need anything installed or configured, just let me know and I can make it so. On Oct 19, 2015 21:01, "Pascal Schumacher" wrote: > I could not figure out if builds.apache.org has the jenkins gradle plugin? > > Also there are already some groovy jobs > https://builds.apache.org/view/Groovy/

Re: Buildserver Github Pull Request Integration (Enabling Travis CI)

I could not figure out if builds.apache.org has the jenkins gradle plugin? Also there are already some groovy jobs https://builds.apache.org/view/Groovy/ but it looks like every build failed. Am 19.10.2015 um 20:54 schrieb Andrew Bayer: Yup, Jenkins can happily do what we need. On Oct 19, 2

Re: Buildserver Github Pull Request Integration (Enabling Travis CI)

Yup, Jenkins can happily do what we need. On Oct 19, 2015 20:49, "Pascal Schumacher" wrote: > Thanks for the info. I did not know that. > > I would also be fine with creating a jenkins job on builds.apache.org (I > use jenkins at work). If my understanding of the information on > https://wiki.apa

Re: Result, was [VOTE] Groovy chairman election...

On Sat, Oct 17, 2015 at 07:38AM, Guillaume Laforge wrote: >So we can't launch the vote yet, and who asks the approval to the board? What I was saying, is that we don't have a PMC until the project is graduated. Having the chair election for the future PMC is totally fine at any point really.

Re: Buildserver Github Pull Request Integration (Enabling Travis CI)

Thanks for the info. I did not know that. I would also be fine with creating a jenkins job on builds.apache.org (I use jenkins at work). If my understanding of the information on https://wiki.apache.org/general/Jenkins is correct, that would also allow us to test on

Re: GROOVY-7635: We should consider upgrading log4j2Version on master to 2.4.1

As far as I know we still are. I personally would prefer dropping support for Java 6. Am 19.10.2015 um 20:23 schrieb Russel Winder: On Mon, 2015-10-19 at 18:01 +0200, Pascal Schumacher wrote: Hello Paul, sadly this is not possible, because Log4J2 requires Java 7 since version 2.3. Else I woul

Re: Buildserver Github Pull Request Integration (Enabling Travis CI)

Fwiw, we can build and update pull requests on builds.apache.org as well. On Oct 19, 2015 20:30, "Pascal Schumacher" wrote: > Hello everybody, > > according to the web TeamCity requires write access to the repo to update > pull requests with test results. As this is not possible to with the Apach

Re: Buildserver Github Pull Request Integration (Enabling Travis CI)

Hello everybody, according to the web TeamCity requires write access to the repo to update pull requests with test results. As this is not possible to with the Apache Github mirror, I suggest we use Travis CI to test pull request. Apache has a subscription for Travis CI https://blogs.apache.

Re: GROOVY-7635: We should consider upgrading log4j2Version on master to 2.4.1

On Mon, 2015-10-19 at 18:01 +0200, Pascal Schumacher wrote: > Hello Paul, > > sadly this is not possible, because Log4J2 requires Java 7 since > version > 2.3. Else I would have updated to 2.4 instead of 2.2 a few weeks ago. > > -Pascal Are we still committing to supporting Java 6? -- Russel.

GROOVY-7635: We should consider upgrading log4j2Version on master to 2.4.1

Hello Paul, sadly this is not possible, because Log4J2 requires Java 7 since version 2.3. Else I would have updated to 2.4 instead of 2.2 a few weeks ago. -Pascal

Re: usage of NumberAwareComparator in extension methods and number oddities (a bit code review)

I opened JIRA issues: https://issues.apache.org/jira/browse/GROOVY-7636 https://issues.apache.org/jira/browse/GROOVY-76367 and created PR: https://github.com/apache/incubator-groovy/pull/150 On Tue, Sep 8, 2015 at 3:19 PM, Thibault Kruse wrote: >> // bug, returns 47? >> // assert compareTo('aa1'