Web applications and other non-Maven applications often require manual deployment of JARs. This can be very difficult with JBoss DNA, considering the number of artifacts and the number of dependencies. We should include as part of our release one (or several) "convenience" JARs that can be used in different situations.

One might be a JAR that contains the JCR implementation, all extensions, and all third-party dependencies (without the logging JARs?). This would be useful when deploying our JCR implementation to a web server via JNDI.

Another might contain our JCR implementation and all extensions, but no third-party dependencies.

Ideally we can identify the real-world scenarios so that produce only those artifacts that are useful.