[teiid-issues] [JBoss JIRA] (TEIID-3503) Use of ModelMetaData required teiid-admin jar

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy resolved TEIID-3503.
---------------------------------
           Labels: CR1  (was: )
    Fix Version/s: 8.11
       Resolution: Done


Introduced a new module called "jboss-admin" and moved the JBoss specific classes and their dependencies to this module. Now only "jboss-integration" and "test-integration" depend on this new "jboss-admin" module, rest others will keep using the "admin" as before.

This should remove the earlyaccess maven repo type transitive dependencies for the embedded.

Checked for kitting and runtime errors.

> Use of ModelMetaData required teiid-admin jar
> ---------------------------------------------
>
>                 Key: TEIID-3503
>                 URL: https://issues.jboss.org/browse/TEIID-3503
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: Embedded
>    Affects Versions: 8.10
>            Reporter: Michael Davies
>            Assignee: Ramesh Reddy
>            Priority: Minor
>              Labels: CR1
>             Fix For: 8.11
>
>
> We are using Embedded and specifically ModelMetaData, for specifying VDB. 
> ModelMetaData class comes from teiid-admin project, which pulls in a lot of AS dependencies, some of which are only available from earlyrelease maven repo.
> For example - org.jboss.as:jboss-as-parent:pom:7.4.0.Final-redhat-4
> So essentially users developing against released teiid API (using ModelMetaData) now have dependency on earlyaccess repo. 
> Where I work the people who manage the internal company repo do not like proxying non-release repos, and so this causes a bit of a pain.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)