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

[Michael Davies (JIRA)]

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

Michael Davies commented on TEIID-3503:
---------------------------------------

teiid-parent-8.10.0.Final pom depends upon 
<version.org.jboss.as>7.4.0.Final-redhat-4</version.org.jboss.as>

Now as far as I can see 7.4.0.Final-redhat-4 is available on here only 

          <id>jboss-earlyaccess</id>
          <name>JBoss Early Access</name>
          <url>https://maven.repository.redhat.com/earlyaccess/all/</url>

So this is not restricted to embedded users. Any devs using teiid need  access to this earlyrelease repo. 




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