[jbosstools-issues] [JBoss JIRA] (JBIDE-10495) Define how BPEL users handle JBoss BPEL migration

[Len DiMaggio (JIRA)]

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

Len DiMaggio commented on JBIDE-10495:
--------------------------------------

>From Bob:

The only difference between the "Legacy BPEL project" and the current one is the project facet ID. Some history: When JBoss created the initial BPEL code fork from eclipse about 4 years ago (before I inherited the project), the decision was made to change the project facet ID from bpel.facet.core to jbt.bpel.facet.core, and the JBoss AS deployment plugin was changed accordingly. At some point during the JBT 3.x release it was decided that we really only needed one facet ID since nothing had changed in the deployment plugins and the default facet ID was changed back to bple.facet.core but the jbt.bpel.facet.core ID was kept for backward compatibility. There are no functional differences between the projects.

                
> Define how BPEL users handle JBoss BPEL migration
> -------------------------------------------------
>
>                 Key: JBIDE-10495
>                 URL: https://issues.jboss.org/browse/JBIDE-10495
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: BPEL
>    Affects Versions: 3.3.0.Beta1-SOA
>            Reporter: Max Rydahl Andersen
>            Assignee: Robert (Bob) Brodt
>            Priority: Blocker
>             Fix For: 3.3.0.Beta2-SOA
>
>
> JBDS-1909 is talking about keeping the old way of creating JBoss Legacy BPEL projects without outlining how migration works
> and which packaging approach is used.
> I want to be aligned on what this migration means:
> It seems we will have:
> 2 different facets old jboss and new bpel
> 2 different packaging - one using WTP style packaging that is compatible with JBoss AS adapters (old jboss) and one using non-WTP style packing which is not compatible with anything but specific tomcat server adapter (new jboss)
> 2 different wizards for creating projects
> And could we please not keep old packaging styles around if we could just migrate them over one way or the other.
> And please let us not make *another* deployment/packaging approach.
> I hope i'm wrong in the above observations so please let us once and for all document what the migration plan is and what reality we have ;)
>  

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