since both jars use the same bundle Id it can come to clashes when both are used in osgi environments.

We are using sonar nexus repository server with p2 plugin which generates p2 metadata from all jar files that contain a valid osgi'fied MANIFEST.MF file.

So we can import thirdparty libraries to an eclipse target platform with a .target file like that:
<location includeAllPlatforms="false" includeConfigurePhase="false" includeMode="slicer" includeSource="true" type="InstallableUnit">
<unit id="slf4j.api" version="1.7.2"/>
<repository location="http://build.godyo.int:8081/nexus/content/repositories/central/.meta/p2/"/>
</location>

The odd thing was that we got MD5 errors when setting the target platform, but only on some machines.

In the end it showed that the nexus server hat the slf4j.api and it corresponding test jar. Both with the same Bundle Id and so something got mixed up.

the test jar should have a Bundle Id like slf4g.api.test