Version 10

    All JBoss projects must follow the groupId/artifactId guidelines (MavenProjectNaming).


    Note that the groupId "jboss" is deprecated and should be replaced by "org.jboss".  For more information, see Maven JBoss GroupIds


    Source Jars


    During the release staging process, Nexus will verify that each artifact in your release must have an associated source jar.  For example an project which produces my-jboss-project-1.0.jar, must also produce my-jboss-project-1.0-sources.jar.


    Pom Validation


    All JBoss project POMs must contain (or inherit from a parent pom) the following information:


    • modelVersion
    • groupId
    • artifactId
    • version
    • packaging (defaults to jar)
    • name
    • description
    • url
    • licenses
    • scm/url
    • scm/connection
    • scm/developerConnection
    • developers


    The field scm/url should contain the project fisheye URL (

    If you set the parent pom to org.jboss:jboss-parent version 5 or higher, then default values are provided for all the fields.


    Things Not to include

    Since every artifact in jboss repo is mirrored to Maven central many projects have a tendency to include repository information in their pom.xml.


    That makes it easy to build out of the box but it also leaks that repository information into all projects that uses your pom and thus your project can be affecting which repository a users build are using which can result in hard to trace and debug issues concerning dependency resolution.


    Thus do not include repository info in your pom files - if you want to provide an easy way to get the list of suggested repositories include a settings.xml into your project and use "mvn -s settings.xml" when building the project.


    POM Template


    <project xmlns="" xmlns:xsi="" xsi:schemaLocation="">
      <name>[project name]</name>
      <description>[project description]</description>
      <url>[project url]</url>
          <name>[license name]</name>
          <url>[license url]</url>
        <url>[path to repo]</url>
        <connection>[path to repo]</connection>
        <developerConnection>[path to repo]</developerConnection>
          <id>[ username]</id>
          <name>[developer name]</name>
          <organization>[developer organization]</organization>