Uploaded image for project: 'JBoss Developer Materials'
  1. JBoss Developer Materials
  2. JDF-96

Make JBoss BOMs standalone (remove jboss-parent)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • jdfsite-1.0.5.Final
    • stacks
    • None

      All JBoss BOMs specify org.jboss:jboss-parent as a parent. The parent is used to share pluginManagement configuration across various JBoss project in community.

      However, during productization effort, the parent is modified which has following consequences for every JBoss BOM:

      1/ Version management in <properties> is propagated to the BOM, which might influence versions in both plugins and dependencies in an unexpected way
      2/ Any dependencies specified in <dependencyManagement> of an upper pom (e.g. productized jboss-parent up to root) are included as well if a JBoss BOM is imported in <dependencyManagement>
      3/ Plugin management is configured to use enterprise plugins, which are not available to the outside world

      As a note, current hierarchy of productized jboss-parent:8-redhat-1 (jboss-parent -> jboss-component-version-master) together with recommended usage, that is the BOM is used to import dependencies only, does not break points 2/ and 3/.

      This effort reflects following community changes already done:

            rafabene_jira Rafael Benevides (Inactive)
            kpiwko Karel Piwko
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: