Issue
From jBoss 4.2 to 5.0 the decision was made to change jbossall-client.jar to be an empty jar, referring to other jars via the manifest classpath. Unfortunately this significantly increases the maintenance burden for developers, particularly those using maven. Rather than simply add a single dependency to a project pom we must now add a dependency for each entry in the manifest classpath.

Resolution
Publish a pom for jbossall-client that describes all necessary dependencies to the jboss maven repo. The problem would be solved using maven transitive dependencies.

Further detail
This point has already been raised by Bill Burke elsewhere: http://lists.jboss.org/pipermail/jboss-development/2008-February/011420.html