[teiid-issues] [JBoss JIRA] (TEIID-3503) Development with Embedded teiid should not require dependency on EAP

[Ramesh Reddy (JIRA)]

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

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

Steve, I see what you are saying, I think we can fix this by getting rid of all the EAP dependencies from parent POM, then create another child project like "connectors" then move the dependencies in there, then also move "jboss-integration", "jboss-security" and "jboss-admin" under this child as sub projects. Moving them is easy not sure the extent of the kitting changes. Should we consider this for 8.11? 

> Development with Embedded teiid should not require dependency on EAP
> --------------------------------------------------------------------
>
>                 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)