Re: Proposal: Statically compileable builders

2016-10-06 Thread Cédric Champeau
I prefer to support different _methodMissing_ methods taking different arguments, because they can participate in method selection and return a more specific type. Something to consider too: @DelegatesTo is not on par with @ClosureParams wrt to the types it can express. In particular, it doesn't h

Re: Proposal: Statically compileable builders

2016-10-06 Thread Jochen Theodorou
On 06.10.2016 09:16, Cédric Champeau wrote: I prefer to support different _methodMissing_ methods taking different arguments, because they can participate in method selection and return a more specific type. Something to consider too: @DelegatesTo is not on par with @ClosureParams wrt to the t

Re: Groovy build fail

2016-10-06 Thread Russel Winder
It appears that the build is now working fine on JDK9 138. Well the install and installGroovy tasks anyway. I guess I need to now try with the distDoc task as well. -- Russel. = Dr Russel Winder t: +44 20 7585 2200

Re: Proposal: Statically compileable builders

2016-10-06 Thread Graeme Rocher
On Thu, Oct 6, 2016 at 10:45 AM, Jochen Theodorou wrote: > > > On 06.10.2016 09:16, Cédric Champeau wrote: >> >> I prefer to support different _methodMissing_ methods taking different >> arguments, because they can participate in method selection and return a >> more specific type. >> >> Something

Re: [PROGRESS REPORT 20161004]groovy-parser

2016-10-06 Thread Graeme Rocher
That is awesome, keep up the good work. Cheers On Wed, Oct 5, 2016 at 5:57 AM, daniel_sun wrote: > Thanks :) > > > > -- > View this message in context: > http://groovy.329449.n5.nabble.com/PROGRESS-REPORT-20161004-groovy-parser-tp5735725p5735778.html > Sent from the Groovy Dev mailing list arch

答复: [PROGRESS REPORT 20161004]groovy-parser

2016-10-06 Thread daniel_sun
Hi Graeme, The last test result is shown as following: https://travis-ci.org/danielsun1106/groovy/builds/165263810 13395 tests completed, 3 failed, 9 skipped Currently I'm trying to solve the following issue, which blocks me to verify issues. It's pity that I'm not very familiar

Re: 答复: [PROGRESS REPORT 20161004]groovy-parser

2016-10-06 Thread Graeme Rocher
Hi Daniel, Yes I have seen that before, it happens when Travis runs out of memory since each Travis build is limited by memory. Try split up the steps that compile the code with the steps that run the tests and also avoid using the Gradle daemon: ./gradlew compileGroovy --no-daemon ./gradlew comp

答复: 答复: [PROGRESS REPORT 20161004]groovy-parser

2016-10-06 Thread daniel_sun
Hi Graeme, Thanks for your help! I'll give it a try :) PS: The new parser requires Java8 because streams and lambda expression are used. Cheers, Daniel.Sun 发件人: Graeme Rocher-2 [via Groovy] 发送时间: 2016年10月6日 18:27 收件人: daniel_sun 主题: Re: 答复: [PROGRESS

Groovy build on JDK9 OK but only without the docs

2016-10-06 Thread Russel Winder
I recollect this is a "known problem", but have forgotten what the answer was. Do we know what we have to campaigh for to get whatever it is fixed so this isn't broken? :asciidoctorAssets FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':asciidoctor'. > ja

Re: 答复: 答复: [PROGRESS REPORT 20161004]groovy-parser

2016-10-06 Thread Graeme Rocher
Oh, it could be a problem dropping Java 7 support if this were ever contributed to Groovy core Cheers On Thu, Oct 6, 2016 at 12:44 PM, daniel_sun wrote: > Hi Graeme, > > >Thanks for your help! I'll give it a try :) > > > PS: The new parser requires Java8 because streams and lambda expres

Re: 答复: 答复: [PROGRESS REPORT 20161004]groovy-parser

2016-10-06 Thread daniel_sun
As far as I know, Groovy will migrate to Java8 as soon as possible, so it will be OK in the near future ;) 在 "Graeme Rocher-2 [via Groovy]" ，2016年10月6日 下午8:19写道： Oh, it could be a problem dropping Java 7 support if this were ever contributed to Groovy core Cheers On Thu, Oct 6, 2016 at 12:4

Re: 答复: 答复: [PROGRESS REPORT 20161004]groovy-parser

2016-10-06 Thread Paul King
I didn't realise Java 8 was a requirement. I was hoping we could maybe even sneak the new parser into Groovy 2.5 (but not turned on by default) since we have been delayed so long and the parser is coming along nicely. Given the Java 8 requirement, that might be a bit more work than we originally p

Re: Groovy build on JDK9 OK but only without the docs

2016-10-06 Thread John Wagenleitner
On Thu, Oct 6, 2016 at 3:46 AM, Russel Winder wrote: > > I recollect this is a "known problem", but have forgotten what the > answer was. Do we know what we have to campaigh for to get whatever it > is fixed so this isn't broken? > > > :asciidoctorAssets > > FAILURE: Build failed with an exceptio

Re: Groovy build on JDK9 OK but only without the docs

2016-10-06 Thread Russel Winder
On Thu, 2016-10-06 at 21:18 -0700, John Wagenleitner wrote: > […] > If memory serves me, updating the asciidoctor-gradle-plugin from > 1.5.2 to > 1.5.3 fixed the build issue but introduced a formatting issue with > tables > [1].  The formatting issue affected all builds not just jdk9 builds. > >

Re: 答复: 答复: [PROGRESS REPORT 20161004]groovy-parser

2016-10-06 Thread daniel_sun
How about providing a jar file containing the new parser, which is compiled by Java8. When developers use Java8, they can try the new parser by turning on the switch. Cheers, Daniel.Sun 在 "paulk_asert [via Groovy]" ，2016年10月7日 上午4:55写道： I didn't realise Java 8 was a requirement. I was hopin