Hi Robert,
I was investigating this issue long. The problem was with IDEA. Yesterday I
installed new version 2019.2 and set JDK 1.7 as system JAVA_HOME but the
project used JDK 1.8, see [1].
Suddenly, the maven-invoker-plugin used JAVA_HOME from the system and not
from IDEA settings. It wasn't pro
Am 2019-07-20 um 12:25 schrieb Hervé BOUTEMY:
As a side note, I started by doing a lot of cleanup on old merged branches: it
would be nice if everybody did its own cleanup when merging
I have purged all of my merged branches, there are still a lot of open
branches...
---
Hi Tibor,
off topic, but step 3 should of course be verify...
I can't reproduce it, nor can Jenkins@ASF, see
https://builds.apache.org/job/maven-box/job/maven-resolver/job/master/
Based on the exception I would expect that the runtime is Java 7, not Java
8.
Please verify the complete logfile,
Hi Robert,
I have very similar issue in apache/maven-resolver on my PC.
I don't know if the root cause is identical with the one you described in
your email regarding the parameter mavenOpts and shared environment
variable but I am sure you can reproduce it too.
These are my reprosteps:
1. clone
Looks like the same issue as there was with the maven site plugin: the
failing it was using mavenOpts as well.
I'm pretty sure that mavenOpts is not isolated and can be changed by any
other process on the same server.
Instead one should be using test.properties to pass those properties,
which
