[teiid-issues] [JBoss JIRA] (TEIID-5563) Separate the Teiid WildFly distribution into their own repo or module

[Ramesh Reddy (Jira)]

     [ https://issues.jboss.org/browse/TEIID-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramesh Reddy updated TEIID-5563:
--------------------------------
    Description: 
With the different types of distributions now being built based on Teiid like
* WildFly
* Thorntail
* SpringBoot
* Embedded

Having main `github.com/teiid` repo contain artifacts for WildFly distribution poses an unnecessary dependency burden on other distributions. For example, all the resource adapters in the repo are only useful in WildFly and Thorntail V2. However, when they are pulled into environments like SpringBoot they will bring the whole dependency chain with them with some JEE constructs that are unnecessary. This proposal is to separate "teiid" core modules along with all translators into one repository and move all the resource adapters along with any feature-packs and module building into a sperate repository like "teiid-wildfly".

Basically, when finished, the core Teiid modules only provide Maven artifacts along with their clean pom.xml with for direct and maybe transitive dependencies. None of the WildFly based modules support will be here.

The "teiid-wildfly" module on the other hand, will exactly preserve what is in the current repo as far feature packs and module building and overall WildFly distribution building.

A follow-on task we can task we can look into is, converting the main teiid then to use basepom rather than the jboss-parent pom. However, the recommendation is this should be done after, not simultaneously.



  was:Separate the Teiid connectors into their own repo to make it easier to manage the Teiid project dependencies separate from the connectors.   

        Summary: Separate the Teiid WildFly distribution into their own repo or module  (was: Separate the Teiid connectors into their own repo)


> Separate the Teiid WildFly distribution into their own repo or module
> ---------------------------------------------------------------------
>
>                 Key: TEIID-5563
>                 URL: https://issues.jboss.org/browse/TEIID-5563
>             Project: Teiid
>          Issue Type: Task
>          Components: Build/Kits, Integration Tests
>    Affects Versions: 12.x
>            Reporter: Van Halbert
>            Assignee: Van Halbert
>            Priority: Major
>
> With the different types of distributions now being built based on Teiid like
> * WildFly
> * Thorntail
> * SpringBoot
> * Embedded
> Having main `github.com/teiid` repo contain artifacts for WildFly distribution poses an unnecessary dependency burden on other distributions. For example, all the resource adapters in the repo are only useful in WildFly and Thorntail V2. However, when they are pulled into environments like SpringBoot they will bring the whole dependency chain with them with some JEE constructs that are unnecessary. This proposal is to separate "teiid" core modules along with all translators into one repository and move all the resource adapters along with any feature-packs and module building into a sperate repository like "teiid-wildfly".
> Basically, when finished, the core Teiid modules only provide Maven artifacts along with their clean pom.xml with for direct and maybe transitive dependencies. None of the WildFly based modules support will be here.
> The "teiid-wildfly" module on the other hand, will exactly preserve what is in the current repo as far feature packs and module building and overall WildFly distribution building.
> A follow-on task we can task we can look into is, converting the main teiid then to use basepom rather than the jboss-parent pom. However, the recommendation is this should be done after, not simultaneously.



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