[jbosstools-issues] [JBoss JIRA] (JBDS-2123) Unable to install SOA-P Tooling from Central

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBDS-2123 at 5/7/12 1:18 PM:
----------------------------------------------------------

https://devstudio.jboss.com/updates/5.0/staging/soa-tooling/ updated to include ../ site (which in turn includes latest JBDS Core & TP sites).

Also removed flow.feature from central connector in trunk (but NOT in soatools beta1 branch) because jbpm3 does not need it - IIRC that's just for jbpm4.
                
      was (Author: nickboldt):
    https://devstudio.jboss.com/updates/5.0/staging/soa-tooling/ updated to include ../ site (which in turn includes latest JBDS Core & TP sites).

Also removed flow.feature from central connector because jbpm3 does not need it - IIRC that's just for jbpm4.
                  
> Unable to install SOA-P Tooling from Central
> --------------------------------------------
>
>                 Key: JBDS-2123
>                 URL: https://issues.jboss.org/browse/JBDS-2123
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: central, SOA Tooling / Platform , updatesite
>    Affects Versions: 5.0.0.Beta1-SOA
>         Environment: JBDS 5.0.0.Beta3
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/5.0/devstudio-directory.xml
> OpenJDK 1.6 64b
> Fedora16 64b
>            Reporter: Radim Hopp
>            Assignee: Douglas Palmer
>             Fix For: 5.0.0.Beta1-SOA
>
>         Attachments: JBDS2123-patch-fix-bpel-missing-feature-and-plugin.txt, soa-p-tooling-cannot-install-bpel-missing-eclipse.org-plugin.png, SOA-PInstall.png
>
>
> Can't install SOA-P Tooling.
> See attached screenshot.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira