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 changing the scope to test, you are actually
reducing its scope: the dependency will only be used during the test-phase.
So the fix is simple: don't give the artifact the test-scope, but the
compile scope.
A good improvement would be that Maven warns if it detects that a scope is
reduced for a specific dependency.
regards,
Robert
Op Thu, 17 Sep 2015 14:09:30 +0200 schreef Karl Heinz Marbaise
<[email protected]>:
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: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
