[teiid-issues] [JBoss JIRA] (TEIID-5577) Create clean dependencies / separate boms

[Van Halbert (Jira)]

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

Van Halbert commented on TEIID-5577:
------------------------------------

sure, jboss-dependency-bom, and a child of build-configuration

as for wildfly-parent, wouldn't it be:    wildfly-parent imports  teiid-bom and wildfly-bom

as to the teiid+shared bom, why not just have the teiid root pom import both the teiid-bom and jboss-dependency bom, then no need for another bom, and the wildfly parent would then import them both too, beside the wildfly bom


> Create clean dependencies / separate boms
> -----------------------------------------
>
>                 Key: TEIID-5577
>                 URL: https://issues.jboss.org/browse/TEIID-5577
>             Project: Teiid
>          Issue Type: Sub-task
>          Components: Build/Kits
>            Reporter: Steven Hawkins
>            Assignee: Van Halbert
>            Priority: Major
>
> The teiid-bom currently defines all of the non-overlapping dependencies with the wildfly bom.  
> We should introduce another bom that defines the overlapping dependencies used by the core project - this includes things like vfs, jboss-logging, the javax api jars, marshalling, infinispan, etc.  We should also substitute usage of the jboss javax jars for whatever the vanilla replacements are.
> We should then be able to cut ties with wildfly boms in the core project.
> For connector development convenience we could also introduce a bom-wildfly which imports both the teiid-bom and the wildfly-parent.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)