[jbosstools-issues] [JBoss JIRA] (JBDS-2388) Tracker issue - JBDS6 and SOA Tooling Issues

[Len DiMaggio (JIRA)]

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

Len DiMaggio commented on JBDS-2388:
------------------------------------

* And this jBPM bug - where the correct perspective is not opened:
- https://bugzilla.redhat.com/show_bug.cgi?id=881131
                
> Tracker issue - JBDS6 and SOA Tooling Issues
> --------------------------------------------
>
>                 Key: JBDS-2388
>                 URL: https://issues.jboss.org/browse/JBDS-2388
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: SOA Tooling / Platform 
>    Affects Versions: 5.0.0.GA-SOA
>            Reporter: Len DiMaggio
>            Assignee: Douglas Palmer
>             Fix For: 6.0.0.Alpha1-SOA
>
>
> Summary of current blocking bugs for SOA Tooling, inc. JBDS 6.0 (Eclipse Juno) 
> Tracker bug: https://issues.jboss.org/browse/JBDS-2388
> * Tooling Install onto JBDS 6.0 is blocked by SOA 5.3 tooling's dependency on Eclipse 3.7:
> - JBDS: https://issues.jboss.org/browse/JBDS-2269
> - SOA: https://bugzilla.redhat.com/show_bug.cgi?id=855097
> - BRMS: https://bugzilla.redhat.com/show_bug.cgi?id=855100
> * API Change Issue - Cannot install the ESB tools and ESB detector with Juno
> - https://issues.jboss.org/browse/JBIDE-12061
> * Related SwitchYard tooling issue
> - https://issues.jboss.org/browse/JBDS-2374
> * And other tooling install bug:
> - https://issues.jboss.org/browse/JBIDE-12936
> * And this SOA related bug in JBDS core - https://issues.jboss.org/browse/JBDS-2365 - blocks deploying to SOA servers.
> In SOA 6, a corresponding fix should be made to move the property to SOA tooling - 
> https://issues.jboss.org/browse/JBDS-2406, https://bugzilla.redhat.com/show_bug.cgi?id=880647

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