[jbosstools-issues] [JBoss JIRA] (JBTIS-86) JBTIS 4.0.1 Component Content - SOA-P 6 Alpha 2 (Juno)

[Paul Leacu (JIRA)]

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

Paul Leacu commented on JBTIS-86:
---------------------------------

Update SwitchYard and Teiid

https://github.com/jbosstools/jbosstools-integration-stack/commit/f0f08e7c781e6855828a5386c72185899d9c3b8e
                
> JBTIS 4.0.1 Component Content - SOA-P 6 Alpha 2 (Juno)
> ------------------------------------------------------
>
>                 Key: JBTIS-86
>                 URL: https://issues.jboss.org/browse/JBTIS-86
>             Project: JBoss Tools Integration Stack
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: distribution
>    Affects Versions: 4.0.1
>         Environment: Eclipse Juno
>            Reporter: Paul Leacu
>            Assignee: Paul Leacu
>             Fix For: 4.0.1
>
>
> We're not quite done with Juno...
> The SOA-P PM team has requested a JBTIS 4.0.1 Juno-based tools release for the SOA-P 6 Alpha 2 near the end of June.  As with the JBTIS 4.0.0 SOA-P 6 Alpha, there will not be a JBDSIS associated with this release.  The JBDSIS release will be based on the Kepler/SOA-P 6 Beta.  This is a good opportunity for those components that went to .Final and just missed the 4.0.0 JBTIS to get in now.
> To avoid confusion as we're doing both the Alpha2 and Beta work simultaneously and to make things easier for everyone, I will coordinate the content with a lone master Jira.  Note however that if you'd like to test something the JBTIS master is Kepler-based.  The JBTIS-4.0.x tag should be used to base any changes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira