[jbosstools-issues] [JBoss JIRA] Updated: (JBDS-1810) Push BPEL editor development back upstream to eclipse.org

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBDS-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt updated JBDS-1810:
-----------------------------

    Description: 
The BPEL editor development will be moved back to eclipse.org - JBT/JBDS and SOA builds should include the plugins from the eclipse update site at http://download.eclipse.org/bpel/update-site/

Most of the bundle ids will be the same except for the cheatsheet plugin which will be moving to eclipse.org and will be renamed from org.jboss.tools.bpel.cheatsheet to org.eclipse.bpel.cheatsheet. I was planing on renaming the JBoss/Riftsaw deployment plugin from org.jboss.tools.bpel.runtimes to org.eclipse.bpel.jboss.riftsaw.runtime (since there's already a org.eclipse.bpel.runtimes and following in the naming pattern of org.eclipse.bpel.apache.ode.runtime) but if we're going to keep this plugin at jboss, it'll probably remain the same.



  was:The BPEL editor development will be moved back to eclipse.org - JBT/JBDS and SOA builds should include the plugins from the eclipse update site at http://download.eclipse.org/bpel/update-site/



Bob, please detail for me, for each of these two sites (JBoss Tools - SOA Tooling and JBDS - SOA Tooling, as noted here [1] in JBIDE-9029):

. the list of BPEL features you want sourced from Eclipse
. the list of plugins or features you want to continue to come from JBoss (I may need to add new features or tweak the existing one(s) to properly contain the plugins you need)

[1] https://issues.jboss.org/browse/JBIDE-9029?focusedCommentId=12618959&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12618959

If the list for inclusion in JBT and JBDS is the same, great. But I expect you'll have examples or plugins or tests that live in either the com.* or org.* namespaces, in which case the collection of plugins will be different on the two sites. 

For more on how the plugin to update site inclusion works, and how the subset/superset relationship exists between JBT and JBDS, see these charts:

http://cheezburger.com/nickboldt/lolz

> Push BPEL editor development back upstream to eclipse.org
> ---------------------------------------------------------
>
>                 Key: JBDS-1810
>                 URL: https://issues.jboss.org/browse/JBDS-1810
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>          Components: integration, SOA Platform
>            Reporter: Robert (Bob) Brodt
>            Assignee: Nick Boldt
>             Fix For: 5.0.0.M3
>
>
> The BPEL editor development will be moved back to eclipse.org - JBT/JBDS and SOA builds should include the plugins from the eclipse update site at http://download.eclipse.org/bpel/update-site/
> Most of the bundle ids will be the same except for the cheatsheet plugin which will be moving to eclipse.org and will be renamed from org.jboss.tools.bpel.cheatsheet to org.eclipse.bpel.cheatsheet. I was planing on renaming the JBoss/Riftsaw deployment plugin from org.jboss.tools.bpel.runtimes to org.eclipse.bpel.jboss.riftsaw.runtime (since there's already a org.eclipse.bpel.runtimes and following in the naming pattern of org.eclipse.bpel.apache.ode.runtime) but if we're going to keep this plugin at jboss, it'll probably remain the same.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira