]
Steven Hawkins commented on TEIID-5577:
---------------------------------------
Can we call it jboss-dependency-bom - that matches some of other naming conventions?
Should it be a child of build-configuration?
The wildfly bom will import from the teiid-bom and the wildfly-parent correct?
As for teiid-bom importing the shared dependencies - it may make sense to keep them
separate and also create a teiid-all (teiid+shared) 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.