Bug #7445
Updated by Rob Nahf over 8 years ago
jcs: jcs depends on jdbc-stdext, jdbc-ext, which wasn't locatable in a maven repo. (so clearing a local .m2 repo will reveal the issue).
libclient doesn't use JDBC, so this isn't an issue. According to maven best practices, applications needing this library should be managing the dependency directly, instead of relying on the transitive dependency via libclient_java. (they should be importing it themselves.
JCS also moved recently, but is still at v1.3. groupId has changed from jcs to "org.apache.jcs", this may have something to do with the issue, but did not thoroughly test.
solution was to exclude the dependency in libclient_java pom.
libclient doesn't use JDBC, so this isn't an issue. According to maven best practices, applications needing this library should be managing the dependency directly, instead of relying on the transitive dependency via libclient_java. (they should be importing it themselves.
JCS also moved recently, but is still at v1.3. groupId has changed from jcs to "org.apache.jcs", this may have something to do with the issue, but did not thoroughly test.
solution was to exclude the dependency in libclient_java pom.
