The issue below reared its head again. But it’s not a 3.1 regression, it never really went away. The stack trace for 3.1-rc-1 looks like this.
This time around it fails to find the class org.apache.maven.wagon.StreamWagon… it’s always the Maven Wagon dependency that is causing me problems like this. Unfortunately, this isn’t really reproducible and will probably be gone on our build server by tomorrow since we delete the Gradle cache in a Jenkins cron job.
The main problem is that it is happening rather randomly so people aren’t giving build failures on Jenkins the attention they deserve anymore since it could always be “one of those” failures.
Could you please open a JIRA issue for the classloader pollution problem mentioned by @sterling, or point me to one if it already exists.