[ https://jira.jboss.org/browse/TEIID-1352?page=com.atlassian.jira.plugin.s... ] Ramesh Reddy commented on TEIID-1352: ------------------------------------- IMO, with 7.2 release the API is fairly stable. There are no JIRAs logged against it that might require them to change, may be additions in future releases. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/TEIID-1352?page=com.atlassian.jira.plugin.s... ] John Doyle commented on TEIID-1352: ----------------------------------- If we could get this addressed in either 7.3 or 7.4 then it should enable us to manage across incompatible versions as they arrive. There is no JBoss Tools release on the calendar, nor is there currently a Designer release on the calendar, so I don't really have a preference beyond 7.X. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1352?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1352: --------------------------------------- There is a deep dependency between Teiid/Teiid Designer for parsing/resolving/validation. Breaking the fundamental dependency on the Teiid language objects is desirable for Teiid, but at this point would just fork AST/langauge object/parsing responsibilities over to Designer. Resolving and validation could be handled through sql text based interfaces, but resolving especially should probably also fork so that Designer could be more flexible (line by line/incremental resolving, collecting errors rather than throwing an exception immediately, etc.) It has been our view that we gain so little in the near term by performing this fork and it introduce overhead in keeping both code bases in synch as the language evolves that Teiid Designer is not well equipped to absorb. Just separating out the validation dependency (via a sql text based mechanism) while leaving the language object dependency would not make any sense. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1352?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-1352: ------------------------------------- Yes, admin module is going to be separate in Teiid 8. We can re-consider that once we move the development back into trunk -- 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

[ https://issues.jboss.org/browse/TEIID-1352?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-1352. --------------------------------- Resolution: Done As of T8 Admin interfaces are now are in a separate project. -- 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