[jboss-jira] [JBoss JIRA] (WFLY-4571) Merge the wildfly BOMs into a single BOM

Paul Gier (JIRA) issues at jboss.org
Wed Apr 29 15:23:45 EDT 2015


    [ https://issues.jboss.org/browse/WFLY-4571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064046#comment-13064046 ] 

Paul Gier commented on WFLY-4571:
---------------------------------

How would the tools dependency management affect the test behavior?  For the arquillian deps for example, the BOM should only set the versions of the dependencies if they are already in the build.  They shouldn't have any effect on a build that doesn't have those dependencies.  Same with the wildfly-maven-plugin, since it's in "pluginManagement" instead of "plugins", the BOM should only have the effect of setting the version for the plugin if you already added it to the build.  But I might be missing something.

> Merge the wildfly BOMs into a single BOM
> ----------------------------------------
>
>                 Key: WFLY-4571
>                 URL: https://issues.jboss.org/browse/WFLY-4571
>             Project: WildFly
>          Issue Type: Enhancement
>            Reporter: Paul Gier
>            Assignee: Paul Gier
>
> We had some discussion on the jbossdeveloper list [1] about merging the current wildfly/eap boms into a single one instead of a separate bom for each use case.
> The only problematic BOM might be the hibernate3 bom because this includes dependencies which conflict with the hibernate 4 bom.  So the hibernate 3 bom will probably need to remain separate.
> [1]http://lists.jboss.org/pipermail/jbossdeveloper/2015-April/000347.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


More information about the jboss-jira mailing list