[jbosstools-issues] [JBoss JIRA] (JBTIS-326) Remove Savara from JBoss Tools

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBTIS-326:
-------------------------------------------

okey so I assume this goes for both any new soa-tools builds (indigo/juno) and for current integration stack builds (kepler/luna)

Since nothing planned for indigo/juno/kepler we can probably just let that be and have it include whatever latest version was there and then make this change just about removing savara from Luna (JBDS 8/JBT 4.2.x) based releases.

[~objectiser] does that work for you or is there a need to spend energy to remove it from Kepler based releases too ? 



> Remove Savara from JBoss Tools
> ------------------------------
>
>                 Key: JBTIS-326
>                 URL: https://issues.jboss.org/browse/JBTIS-326
>             Project: JBoss Tools Integration Stack
>          Issue Type: Task
>            Reporter: Gary Brown
>
> Please remove the Savara tools (plugins) from the JBoss Tools distribution.
> Although the underlying principle behind Savara (Testable Architecture) is still a valid and desirable goal, the current implementation based around a graphical model (WS-CDL and then BPMN2 Choreography) has not found support in industry.
> Alternative ways to achieve these goals will be investigated.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)