Karel Piwko created JDF-96: ------------------------------ Summary: Make JBoss BOMs standalone (remove jboss-parent) Key: JDF-96 URL: https://issues.jboss.org/browse/JDF-96 Project: JBoss Developer Framework Issue Type: Bug Components: stacks Affects Versions: 1.0.5.Final Reporter: Karel Piwko Assignee: Rafael Benevides 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: * https://issues.jboss.org/browse/RF-11760 * https://issues.jboss.org/browse/ARQ-843 * https://issues.jboss.org/browse/ARQ-686 * https://issues.jboss.org/browse/SHRINKWRAP-367 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira