How to manage JBoss library and API dependency versions in Maven

Solution Verified - Updated -

Issue

  • Is there a BOM including all specs and JBoss modules with provided scope?
  • What is the correct JBoss stack to include in our POM files so that it includes all Java EE 6 APIs necessary to run Java EE applications?
  • What GAV (groupId, artifactId and version) maven coordinates should be included in the POM files?
  • Is there a single BOM POM for EAP 6 which includes all JBoss maven dependencies?
  • Missing jboss-javaee-all-6.0 in EAP maven repo
  • Missing transitive dependencies in EAP 6.1 cause the maven build to fail
  • We have a web application project with the dependencies and we would like to find out if there will be any issues supporting this setup on our Linux environment. We are running with Java JVM 1.7.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.x
  • Maven

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.