[teiid-issues] [JBoss JIRA] (TEIID-3503) Use of ModelMetaData required teiid-admin jar
Steven Hawkins (JIRA)
issues at jboss.org
Mon Jun 1 10:52:02 EDT 2015
[ https://issues.jboss.org/browse/TEIID-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Hawkins updated TEIID-3503:
----------------------------------
Forum Reference: https://developer.jboss.org/message/932452
Also, this has been expressed in the general teiid development scenarios as well. Beyond the reassurance that alpha / preview EAP releases correspond to stable community releases there may be more that needs to be done here.
> 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)
More information about the teiid-issues
mailing list