[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=12690859#comment-12690859 ] 

Nick Boldt commented on JBDS-2123:
----------------------------------

With BPEL installed from SOA site directly, i get this error instead:

{code}
Cannot complete the install because one or more required items could not be found.
Software being installed: JBoss ESB Tools 1.5.0.v20120427-1932-H1-Beta1-SOA (org.jboss.tools.esb.feature.feature.group 1.5.0.v20120427-1932-H1-Beta1-SOA)
Missing requirement: JBoss ESB Project UI Plugin 1.5.2.v20120427-1932-H1-Beta1-SOA (org.jboss.tools.esb.project.ui 1.5.2.v20120427-1932-H1-Beta1-SOA) requires 'bundle org.eclipse.zest.core 0.0.0' but it could not be found
Cannot satisfy dependency:
{code}

So... I think we need to composite in the JBDS Core/TP site into the JBDS SOA Site to solve missing upstream deps. working on a fix...
                
> 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