Re: About code coverage of Groovy

Thanks, John. Can we check the code coverage for Groovy on travis-ci by default? It will report current code coverage for every commit and PR. Actually, I'm looking for something like this: https://coveralls.io/github/danielsun1106/groovy-parser Cheers, Daniel.Sun -- View this message in

Re: About code coverage of Groovy

I think if you run the 'check' task with -Pcoverage it'll generate the jacoco reports. On Tue, Apr 11, 2017 at 9:27 AM, Daniel Sun wrote: > Hi all, > > Where can I find the code coverage report of Groovy? If there is no > such thing currently, how about supporting

Re: master branch has had the 'parrot' branch merged

Hi Paul, We can place these zip files in some site and make gradle download them before testing. Cheers, Daniel.Sun -- View this message in context: http://groovy.329449.n5.nabble.com/master-branch-has-had-the-parrot-branch-merged-tp5739796p5739809.html Sent from the Groovy Dev

Re: master branch has had the 'parrot' branch merged

Hi Paul, Thanks for your setting aside some time to merge parrot into mater when you are still on holidays. If I got your words, zip files containing other project source code should be excluded in the source distribution, right? When Groovy 3 is applied by these projects,

Re: master branch has had the 'parrot' branch merged

Great news :) Great work guys!! 2017-04-11 3:49 GMT+02:00 Paul King : > > Hi all, > > I merged the parrot branch into master. All the tests pass. > > I'll split off the GROOVY_2_6_X branch next week (the idea of that branch > is outlined in earlier emails) and merge in the