Due to the two issues which were discovered and given we now have fixes, I'm going to restart the release process with those fixes included. While both issues are somewhat edge cases, they were masked in previous versions of Groovy due to other bugs, so it will be a much more seamless upgrade to fix them straight away.

Tomorrow, I'll take a quick look at:


And also include a fix for that if I can work out an easy fix - otherwise I'll produce the next candidate without it. If anyone else has time to look at that issue in the meantime it would be much appreciated.

cheers, Paul.

On Wed, Nov 15, 2017 at 10:10 AM, Daniel Sun <realbluesun@hotmail.com> wrote:


Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html