[ https://jira.jboss.org/jira/browse/TEIIDDES-175?page=com.atlassian.jira.p... ] John Doyle updated TEIIDDES-175: -------------------------------- Parent: TEIIDDES-176 Issue Type: Sub-task (was: Feature Request) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/TEIIDDES-175?page=com.atlassian.jira.plugin... ] John Doyle updated TEIIDDES-175: -------------------------------- Summary: Create a target platform for Teiid deployments that is capable of resolving the required Admin API jars and the Client jars. (was: Define a contract beween Teiid and Designer that enables Designer to use different versions of Teiid.) Fix Version/s: Future (was: 7.1.1) Description: Requirements: 1) JBoss Tools interacts with it's runtimes via user selection of the target platform (typically through the Preferences Dialog). Designer should also adhere to this paradigm as much as possible rather than package the runtime jars. 2) Teiid Designer should be able to execute models/VDBs with different versions of Teiid. In order to accomplish this in a user friendly manner, a contract should be agreed upon between Teiid and Designer. Designer could invoke Teiid via this contract and the user would be able to easily repoint Designer to different/multiple versions of Teiid in order to test models/VDBs across different versions. was:Teiid Designer should be able to execute models/VDBs with different versions of Teiid. In order to accomplish this in a user friendly manner, a contract should be agreed upon between Teiid and Designer. Designer could invoke Teiid via this contract and the user would be able to easily repoint Designer to different versions of Teiid in order to test models/VDBs across different versions. -- 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/TEIIDDES-175?page=com.atlassian.jira.plug... ] John Doyle updated TEIIDDES-175: -------------------------------- Parent: (was: TEIIDDES-176) Issue Type: Feature Request (was: Sub-task) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIIDDES-175?page=com.atlassian.jira.plug... ] Max Rydahl Andersen commented on TEIIDDES-175: ---------------------------------------------- note, this is not really JBoss Tools specific - the usecase is that from a user perspective you can/will end up using multiple versions of a runtime when being an IDE user; and that at build time its easier to manage if plugins has a *loose* coupling to the runtimes to avoid having the situation of holding back either IDE or runtime releases because their are last minute changes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira