[jbosstools-issues] [JBoss JIRA] (JBTIS-78) Teiid - Kepler component content - JBTIS 4.1.0

[Paul Leacu (JIRA)]

     [ https://issues.jboss.org/browse/JBTIS-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Leacu resolved JBTIS-78.
-----------------------------

    Resolution: Done


Upgraded Teiid to 8.2.0-Alpha2 for JBTIS-4.1.0 - Kepler.
                
> Teiid - Kepler component content - JBTIS 4.1.0
> ----------------------------------------------
>
>                 Key: JBTIS-78
>                 URL: https://issues.jboss.org/browse/JBTIS-78
>             Project: JBoss Tools Integration Stack
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: teiid
>    Affects Versions: 4.1.0.Beta1
>            Reporter: Paul Leacu
>            Assignee: Barry LaFond
>             Fix For: 4.1.0.Beta1
>
>
> Welcome to Kepler.
> JBTIS 4.1.0/JBDSIS 7.0.0 is now available on master/trunk. This is needed for JBDS 7.0 in SOA-P 6.0 Beta. Please specify your compatible component for Kepler and update your contribution to the integration stack. The release procedure is here:
> https://community.jboss.org/wiki/IntegrationToolingReleaseProcess
> The specific files to change are:
> https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jbosstools/site/compositeArtifacts.xml
> https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jbosstools/site/compositeContent.xml
> https://github.com/jbosstools/jbosstools-integration-stack/blob/master/devstudio/site/compositeArtifacts.xml
> https://github.com/jbosstools/jbosstools-integration-stack/blob/master/devstudio/site/compositeContent.xml
> The Kepler JBTIS target platform is here:
> https://repository.jboss.org/nexus/content/repositories/snapshots/org/jboss/tools/integration-stack/target-platform/4.1.0-SNAPSHOT/
> I'll process the PR and regenerate the aggregate update site.
> Thanks!
> --paull

--
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