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

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072820#comment-13072820 ] 

Steven Hawkins commented on TEIID-3503:
---------------------------------------

> Any devs using teiid need access to this earlyrelease repo.

That is correct and is what I was referring to in the previous comment.  The central issue is that for practical purposes it's best to keep our project aligned with the our product mainline, which targets current EAP releases.  Since JBoss/Red Hat wants to further delineate projects and product there is no corresponding community release to match the later EAP releases.  The closest are the EAP alphas.  As you can see however there are some issues with the model and layered community projects.

> Either create like "admin-jboss-integration" or move to "jboss-integration" module.

You'd probably need a new module to keep the adminshell from picking up the jboss-integration dependencies.  

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