The "binaries" JAR for -commons still contains some classes that have been refactored to the -api JAR, which results in duplicates of the classes in the classpath, and mismatched source/binary JARs.

Example mismatched JAR pair (which may not exist by the time you read this - attaching in case):

• infinispan-commons-5.1.0-20111117.100128-2
  • sources
  • binaries

Several packages are affected, including:

• org.infinispan.executors
• org.infinispan.lifecycle
• org.infinispan.manager

This seems to be related to commit 907621288ee8c84d4db64dbf0e6acfb954a8e12f in which several of these classes were re-factored from -commons to -api. For whatever reason, the classes are showing up in the binary builds of both -commons AND -api. Problem present in BETA4 and recent SNAPSHOT builds.

Sorry, my Maven skillz are really too weak to suggest a patch/fix, but it's definitely causing issues trying to trace through stuff in my dev environment.