[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:comment-tabpanel&focusedCommentId=13072931#comment-13072931 ] 

Ramesh Reddy commented on TEIID-3503:
-------------------------------------

The parent pom has references to version of the EAP in property. The dependencies are defined in the <dependencyManagement> not in <dependency>, so not sure how this will affect the pulling in dependencies for embedded. May be maven is somehow obscurely adds this in, may be you guys can explain little further.

My primary goal for JIRA for was not pull in EAP transitive dependencies when one mentions the dependency on "admin" module.  I think that can be achieved with the code changes.

Certainly we can not remove "earlyaccess" completely from the Teiid build until move down to WildFly based deployments. or build a new module structure that removes all the jboss eap specific dependencies to a separate repo along side the core teiid code.

> 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)