I want to do a release of the plugin very soon. Cleaning up the workspace
is mostly caused by an invoker-report. I also noticed that some
input/outputstreams weren't closed properly, that has been fixed already.
If maven-shared-utils 3.2.1 is a likely cause too, then I'll downgrade
that one. Stable jobs are much more important to me.
thanks,
Robert
On Sat, 12 Jan 2019 09:23:20 +0100, Tibor Digana <tibordig...@apache.org>
wrote:
I think we should downgrade maven-shared-utils to 3.1.0 in the
m-invoker-p
because we found the same problem in surefire:3.0.0-M1.
We did not have time to fix it and I have realized the connection to the
Invoker just now.
Faster than a release is to deploy SNAPSHOT version of the Invoker and
use
it in JAR plugin and we will see again fully working Jenkins build
https://builds.apache.org/job/maven-box/job/maven-jar-plugin/job/MJAR-238/
The precondition is to ask the INFRA to restart all Windows or kill all
Java processes.
T
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org