[jbosstools-issues] [JBoss JIRA] (JBTIS-11) JBossTools Integration Stack :: savara: Verify the component configuration of the initial IS tooling release

[Paul Leacu (JIRA)]

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

Paul Leacu commented on JBTIS-11:
---------------------------------

Hi Paul

The Savara features/plugins all start with org.savara and org.scribble.

The stable release is here: http://downloads.jboss.org/savara/releases/updates/2.x (version 2.0.0.Final)

This site also bundles the Eclipse BPMN2 and BPEL editors, as well as the WS-CDL tools (features/plugins beginning with org.pi4soa). The BPMN2 and BPEL editors have been available as separate releases for some time, so the ones in this update site can be ignored.

However if you could also include the org.pi4soa feature/plugins.

The dev release is here: http://downloads.jboss.org/savara/releases/updates/milestones/current (version 2.1.0.M2 currently)

In M3 the number of plugins will be reduced and the org.scribble plugins will no longer be distributed as plugins, but embedded in a savara plugin.

Regards
Gary



----- Original Message -----
>
>    Hey -
>        I've been working with Rob C to produce an aggregate/composite
>        update site project for the layered release of the JBoss
>        tools integration stack.  The good news is that we've made
>        sufficient progress that we need to know the particulars in
>        more detail.  You're receiving this email because I believe
>        that you can provide some portion of the specifics I need.
>         The aggregated IS capture is 162 plugins - could you please
>        review the attached features and plugins file and...
>
>    1.  Identify which features/plugins you are responsible for (or
>    which most closely 'belong' to you).
>    2.  Specify the location of the most recent stable update
>    site/repository.
>    3.  Identify the full version of the lates release of your
>    plugins.
>
> I'll update the target dependencies, composite and site files and see
> if we can produce an independent layered IS release!
>
> Thanks in advance!
>
>       --paull

                
> JBossTools Integration Stack :: savara: Verify the component configuration of the initial IS tooling release
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: JBTIS-11
>                 URL: https://issues.jboss.org/browse/JBTIS-11
>             Project: JBoss Tools Integration Stack
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: savara
>         Environment: JBT 4.0
>            Reporter: Paul Leacu
>            Assignee: Gary Brown
>
> Please verify your component configuration of the JBoss Integration Stack for a JBoss Tools 4.0 target.
> Also check that all components are compatible with the upstream components defined in the target platform.
> ref:
> https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/aggregate-site/site.xml
> https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/releases/compositeArtifacts.xml - compositeContent.xml
> https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/target-platform/integration-tools.target
> I'm working on getting this project promoted to jbosstools in github. Unitl then please refer to/fork the urls above. There is a best-guess already specified for each component.

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