title: JBoss-provided libraries in Maven-managed Java EE app
body: <p>It's actually pretty unlikely for me, but it seems that there is no direct answer over the net about importing JBoss-provided dependencies into Maven-managed Java EE application to be deployed within it.</p>
  
  <p>AFAIK there are 2 things somehow related to the problem, that is <code>jboss-as-client</code> artifact for external (in sense of JVM) JBoss clients and <code>jboss-as-component-matrix</code> artifact with huge <code>&lt;dependencyManagement&gt;</code> block defining version of the libraries that JBoss uses. The latter artifact is pretty useful since I can use Maven's import scope to have all version properly set up. The one that is missing (AFAIK) i something like <code>jboss-as-client</code> but for deployed Java EE application. Something, that I can depend on with <code>provided</code> scope and have all stuff in the classpath, including platform-related APIs (like EJB or JMS) and AS-specific stuff (like EJB-ext or <code>jboss-messaging</code>) and possibly some other stuff from <code>lib</code>, <code>lib/endorsed</code> and (mainly) <code>common/lib</code> directories. I know that probably a better practice (and religion-compatible) would be to be explicit with dependencies used in modules but the way I'm asking about is much more pragmatic for me (sorry), at least for Java EE applications that really use many standard APIs.</p>
  
  <p>I'm really curious about your way of dealing with such challange. I'm using 5.1.0.GA version of the AS.</p>