I have merged some changes to help with Jacoco integration and a fix
related to short-comings around the modifiers for the GroovyObject methods
either of which might be the cause. I was planning to send out an email to
get further feedback because these on face value benign changes are rather
Hi,
the switch to fine grained artifacts with groovy-2.5 made it harder to
consistently mange package versions.
Many projects offer a bom pom
(https://www.baeldung.com/spring-maven-bom), that manages all the
packages so users of maven have to just import the bom pom instead of
having to manage
One of the changes in 2.5.3 is a picocli upgrade.
A potentially breaking change is that error messages for things like
missing required options have been improved in picocli-3.6.
If Nextflow uses picocli, and the tests verify the error message text, this
may cause tests to fail.
On Mon, Sep 17,
Dear all,
Currently Groovy breaks the polymorphism contract for the `equals` and
`toString` methods for objects implementing List, Set, Map interfaces. For
example:
class Mylist extends ArrayList {
Mylist(Collection c) { super(c) }
@Override boolean equals(Object o) { throw new
The Nextflow joint build is failing with the latest snapshot version.
http://ci.groovy-lang.org/viewLog.html?buildId=52435
Since I'm not replicate these errors I'm wondering if there's been any
critical change in the latest 2.5.3-SNAPSHOT version.
Cheers,
Paolo
