[teiid-issues] [JBoss JIRA] (TEIID-1352) Produce Admin API jar containing only Interfaces.

[Steven Hawkins (Commented) (JIRA)]

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

Steven Hawkins commented on TEIID-1352:
---------------------------------------

Ramesh, Teiid 8 does separate out admin api correct? 

As for any of the other separation, we could ensure that the engine consumption is cleaner - like in the MMX days with the engine split into two pieces.  That would help prevent leaking dependencies such as what happened with xom/nux.  But it would only marginally reduce the teiid footprint in Designer.  As the previous comment gets at, Designer would need to fork/own a lot of code to truly separate - and that's unlikely to happen.
                
> Produce Admin API jar containing only Interfaces.
> -------------------------------------------------
>
>                 Key: TEIID-1352
>                 URL: https://issues.jboss.org/browse/TEIID-1352
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: AdminApi
>            Reporter: John Doyle
>            Assignee: Steven Hawkins
>
> TEIIDDES-175 requires the creation of a target runtime for Teiid so that the tooling can be further abstracted from changes in Teiid.  In order to accomplish this the tooling requires an Admin API jar containing only interfaces.  The Designer code that depends upon the Admin API could be compiled with this jar, and the plug-in defining the target runtime would load the implementation of the Admin API at runtime. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira