+1
Le dim. 23 déc. 2018 à 03:20, John Wagenleitner
a écrit :
> +1 (binding)
>
> On Thu, Dec 20, 2018 at 4:28 PM Paul King wrote:
>
>>
>> Dear development community,
>>
>> I am happy to start the VOTE thread for a Groovy 2.5.5 release!
>>
>> This release includes 20 bug fixes/improvements as out
+1 (binding)
On Thu, Dec 20, 2018 at 4:28 PM Paul King wrote:
>
> Dear development community,
>
> I am happy to start the VOTE thread for a Groovy 2.5.5 release!
>
> This release includes 20 bug fixes/improvements as outlined in the
> changelog:
>
> https://issues.apache.org/jira/secure/ReleaseN
+1
> On Dec 22, 2018, at 23:37, Andres Almiray wrote:
>
> +1
>
> Build successful on OSX. No errors.
>
> ---
> Java Champion; Groovy Enthusiast
> JCP EC Associate Seat
> http://andresalmiray.com
> http://www.linkedin.com/in/aalmiray
> --
> What goes up
+1
Build successful on OSX. No errors.
---
Java Champion; Groovy Enthusiast
JCP EC Associate Seat
http://andresalmiray.com
http://www.linkedin.com/in/aalmiray
--
What goes up, must come down. Ask any system administrator.
There are 10 types of people in the
Paul suggested that I use a directory with a space in it, and indeed, my
build works fine now:
https://scans.gradle.com/s/4srwbfihneszm
So it seems a couple of our tests don't tolerate spaces in paths...
Anyhow, otherwise, it works, so...
+1 (binding)
Guillaume
On Fri, Dec 21, 2018 at 10:12 A
My build scan FYI
https://scans.gradle.com/s/xhbwibzr453hs
On Fri, Dec 21, 2018 at 9:57 AM Guillaume Laforge
wrote:
> When building from sources (from my new laptop), I'm seeing two test
> failures:
>
> groovy.security.SecurityTest > testConstructorBug FAILED
> junit.framework.AssertionFaile
When building from sources (from my new laptop), I'm seeing two test
failures:
groovy.security.SecurityTest > testConstructorBug FAILED
junit.framework.AssertionFailedError: Security test was expected to run
successfully, but failed (results on System.out)
at junit.framework.Assert.fai
