[
https://issues.jboss.org/browse/TEIID-5577?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5577:
---------------------------------------
So the next step is TEIID-5563 and splitting out wildfly into its own
bom and submodule section?
We are now shooting for:
org.teiid:teiid-bom - just teiid core / translator dependencies including overlap with
wildfly
org.teiid:teiid-parent - imports the teiid-bom
org.teiid:teiid-wildfly-parent - imports the teiid-bom and wildfly parents and is the
parent for stuff under the wildfly module
So just a parent teiid-wildfly-parent that aggregates, no need for a separate bom.
Part of the thinking behind removing the separate overlap bom is that at the end of this
process we could entertain just collapsing the teiid-bom,
teiid-build-configuration-parent, and teiid-parent back into just the teiid-parent.
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)