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 planned - perhaps a plugin-style mechanism would be required? I think 3.0 was the target for Java8+. We would certainly have the new parser there and probably switched on by default - with a switch to fall back (only if we absolutely need it). I don't know what others think. Paul. On Thu, Oct 6, 2016 at 10:39 PM, daniel_sun <realblue...@hotmail.com> wrote: > 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]" <ml-node+[hidden email]>，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:44 PM, daniel_sun <[hidden email]> wrote: > >> 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] <ml-node+[hidden email]> >> 发送时间: 2016年10月6日 18:27 >> 收件人: daniel_sun >> 主题: Re: 答复: [PROGRESS REPORT 20161004]groovy-parser >> >> 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 compileTestGroovy --no-daemon >> ./gradlew test --no-daemon >> >> Also in my experience Java 8 is more memory intensive than Java 7, so >> if you can use Java 7 to build that often helps. >> >> Cheers >> >> On Thu, Oct 6, 2016 at 12:16 PM, daniel_sun <[hidden email]> wrote: >> >>> 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 with gradle and >>> travis >>> CI, so I've asked Cédric and Paul for help. BTW, I can run test cases >>> without any problem on my local machine. >>> >>> [org.gradle.api.tasks.TaskExecutionException: Execution failed for task >>> ':groovy-ant:compileTestGroovy'] >>> org.gradle.process.internal.worker.WorkerProcessException: Failed to run >>> Gradle Compiler Daemon >>> https://github.com/danielsun1106/groovy/issues/4 >>> >>> >>> Graeme, did you encounter some similiar problem like the above >>> ever? >>> >>> Thanks, >>> Daniel.Sun >>> ________________________________ >>> 发件人: Graeme Rocher-2 [via Groovy] <ml-node+[hidden email]> >>> 发送时间: 2016年10月6日 17:29 >>> 收件人: daniel_sun >>> 主题: Re: [PROGRESS REPORT 20161004]groovy-parser >>> >>> That is awesome, keep up the good work. >>> >>> Cheers >>> >>> On Wed, Oct 5, 2016 at 5:57 AM, daniel_sun <[hidden email]> 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 archive at Nabble.com. >>> >>> >>> >>> -- >>> Graeme Rocher >>> >>> >>> ________________________________ >>> If you reply to this email, your message will be added to the discussion >>> below: >>> >>> >>> http://groovy.329449.n5.nabble.com/PROGRESS-REPORT-20161004-groovy-parser-tp5735725p5735829.html >>> To unsubscribe from [PROGRESS REPORT 20161004]groovy-parser, click here. >>> NAML >>> >>> ________________________________ >>> View this message in context: 答复: [PROGRESS REPORT 20161004]groovy-parser >>> >>> Sent from the Groovy Dev mailing list archive at Nabble.com. >> >> >> >> -- >> Graeme Rocher >> >> >> ________________________________ >> If you reply to this email, your message will be added to the discussion >> below: >> >> http://groovy.329449.n5.nabble.com/PROGRESS-REPORT-20161004-groovy-parser-tp5735725p5735833.html >> To unsubscribe from [PROGRESS REPORT 20161004]groovy-parser, click here. >> NAML >> >> ________________________________ >> View this message in context: 答复: 答复: [PROGRESS REPORT >> 20161004]groovy-parser >> >> Sent from the Groovy Dev mailing list archive at Nabble.com. > > > > -- > Graeme Rocher > > > ________________________________ > If you reply to this email, your message will be added to the discussion > below: > http://groovy.329449.n5.nabble.com/PROGRESS-REPORT-20161004-groovy-parser-tp5735725p5735842.html > To unsubscribe from [PROGRESS REPORT 20161004]groovy-parser, click here. > NAML > > > ________________________________ > View this message in context: Re: 答复: 答复: [PROGRESS REPORT > 20161004]groovy-parser > > Sent from the Groovy Dev mailing list archive at Nabble.com.
