Server dependencies come in client's classpath

[mathieucarbou]

Integration tests in Ehcache are not able to detect issues like this:

ehcache/ehcache3#1535

The reason is that Galvan depends on passthrough, and passthrough depends on all tc apis jars (including server apis). Thus, the client's classpath of the integration tests contain all the server apis also.

To have real integration tests, client classpath should stick with client libs and server libs should not come transitively from Galvan.

The proposed solution is to exclude all server jars coming in Galvan from passthrough, and if Galvan code depends on some server libs, then they should be declared in galvan's pom file with a provided scope. This way they won't come into the client's classpath.

[myronkscott]

@mathieucarbou is this still an issue for you?