[jbosstools-issues] [JBoss JIRA] (JBDS-1909) BPEL Editor cannot complete install

[Nick Boldt (Issue Comment Edited) (JIRA)]

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

Nick Boldt edited comment on JBDS-1909 at 12/15/11 2:20 PM:
------------------------------------------------------------

1. Install JBDS from the M5a build:

http://www.qa.jboss.com/binaries/RHDS/builds/development/5.0.0.M5a/201112150534/

2. Add the JBDS 5M5a SOA update site:

http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.M5a.soa-tooling/

3. Install the BPEL feature:

!install-bpel-jbds5m5a_001.png!

4. No dependency issues reported.

!install-bpel-jbds5m5a_002.png!

5. Restart when prompted, then hit File > New > Other and search for BPEL. Two wizards are shown. Selecting the first:

!bpel-jbds5m5a_001.png!

and the second:

!bpel-jbds5m5a_002.png!

yield nearly identical projects.

However, there is ONE minor difference:

!bpel-jbds5m5a_001vs002.png!

Bottom line... no install problem seen. 

Here's what ends up on disk after install:

{code}
$ cd ~/jbdevstudio-product-linux-gtk-x86_64-5.0.0.v201112150534M-H62-M5/studio; find plugins features -maxdepth 1 -name "*.bpel.*" | sort

features/com.jboss.jbds.bpel.feature_1.1.0.v20111215-0130-H77-M5
features/org.eclipse.bpel.apache.ode.runtime.feature_0.8.0.v20111120-0746-H98-CI
features/org.eclipse.bpel.feature_0.8.0.v20111120-0746-H98-CI
features/org.jboss.tools.bpel.feature_1.1.0.v20111208-2118-H36-M5
plugins/com.jboss.jbds.bpel.examples_1.0.0.v20111215-0130-H77-M5
plugins/org.eclipse.bpel.apache.ode.deploy.model_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.apache.ode.deploy.ui_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.apache.ode.runtime_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.cheatsheet_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.common.model_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.common.ui_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.model_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.runtimes_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.ui_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.validator_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.wsil.model_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.xpath10_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.jboss.tools.bpel.runtimes_0.5.0.v20111208-2118-H36-M5.jar
{code}

So... anything need to change? Seems to me that slapping a different label on the wizard won't clearly identify what's different, but if that's enough to make this usable for M5, great.


                
      was (Author: nickboldt):
    1. Install JBDS from the M5a build:

http://www.qa.jboss.com/binaries/RHDS/builds/development/5.0.0.M5a/201112150534/

2. Add the JBDS 5M5a SOA update site:

http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.M5a.soa-tooling/

3. Install the BPEL feature:

!install-bpel-jbds5m5a_001.png!

4. No dependency issues reported.

!install-bpel-jbds5m5a_002.png!

5. Restart when prompted, then hit File > New > Other and search for BPEL. Two wizards are shown. Selecting the first:

!bpel-jbds5m5a_001.png!

and the second:

!bpel-jbds5m5a_002.png!

yield nearly identical projects.

However, there is ONE minor difference:

!bpel-jbds5m5a_001vs002.png!

Bottom line... no install problem seen. 

Here's what ends up on disk after install:

{code}
features/com.jboss.jbds.bpel.feature_1.1.0.v20111215-0130-H77-M5
features/org.eclipse.bpel.apache.ode.runtime.feature_0.8.0.v20111120-0746-H98-CI
features/org.eclipse.bpel.feature_0.8.0.v20111120-0746-H98-CI
features/org.jboss.tools.bpel.feature_1.1.0.v20111208-2118-H36-M5
plugins/com.jboss.jbds.bpel.examples_1.0.0.v20111215-0130-H77-M5
plugins/org.eclipse.bpel.apache.ode.deploy.model_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.apache.ode.deploy.ui_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.apache.ode.runtime_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.cheatsheet_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.common.model_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.common.ui_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.model_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.runtimes_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.ui_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.validator_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.wsil.model_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.eclipse.bpel.xpath10_0.8.0.v20111120-0746-H98-CI.jar
plugins/org.jboss.tools.bpel.runtimes_0.5.0.v20111208-2118-H36-M5.jar
{code}

So... anything need to change? Seems to me that slapping a different label on the wizard won't clearly identify what's different, but if that's enough to make this usable for M5, great.


                  
> BPEL Editor cannot complete install
> -----------------------------------
>
>                 Key: JBDS-1909
>                 URL: https://issues.jboss.org/browse/JBDS-1909
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: SOA Platform, updatesite
>    Affects Versions: 5.0.0.M4
>            Reporter: Pavol Srna
>            Assignee: Nick Boldt
>            Priority: Critical
>             Fix For: 5.0.0.M5
>
>         Attachments: bpel-jbds5m5a_001.png, bpel-jbds5m5a_001vs002.png, bpel-jbds5m5a_002.png, install-bpel-jbds5m5a_001.png, install-bpel-jbds5m5a_002.png, log.txt, screenshot-2.png, screenshot.png
>
>
> I cannot complete install. See log.txt for more details. This problem has a workaround: add target platform (http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_3.3.indigo/latest/) to the eclipse update sites list. Then the install is successful but another problem is present. There are 2 BPEL Editors installed (Eclipse and JBoss) see screenshot-2.

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