[teiid-issues] [JBoss JIRA] (TEIID-5577) Create clean dependencies / separate boms
Steven Hawkins (Jira)
issues at jboss.org
Tue Dec 18 16:22:00 EST 2018
[ https://issues.jboss.org/browse/TEIID-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676038#comment-13676038 ]
Steven Hawkins commented on TEIID-5577:
---------------------------------------
> IMO don't use "jboss" in
Unfortunately we already set that precedent in other artifact names.
> use the project name. If this is "wildfly" use "org.teiid:teiid-wildfly-bom".
It's not quite wildfly - it's for the overlap of the dependencies that we and wildfly use, so its things across the jboss portfolio like netty, vfs, jboss-logging, infinispan, marshalling, staxmapper, etc.. Such that we can have a bom for the Teiid core maven modules that is free of the wild-parent and wildfly-core-parent poms.
> 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)
More information about the teiid-issues
mailing list