the IT is attached to the issue, but the explanation is quite simple.
When Maven collects all dependencies and it finds different dependencies
with the same groupId+artifactId, it'll pick the version closest to the
project.
A dependency can have only one scope.
So what happens is that by ch
Hi Robert,
you have mentioned that you have an integration test for this issue...
Is it part of the code ? Cause i can't find a related test case / IT
case for it ?
Kind regards
Karl Heinz Marbaise
-
To unsubscribe, e-mail: d
