[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8533) Add migration path for SOA-P 5.1 to 5.2 for BPEL project facets

[Robert (Bob) Brodt (JIRA)]

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

Robert (Bob) Brodt commented on JBIDE-8533:
-------------------------------------------

Deprecated the "jbt.bpel.facet.core" facet ID in favor of "bpel.facet.core" (this is the same ID as that in the eclipse.org BPEL Designer project. Backward compatibility with SOA-P 5.1 runtime was kept.

The migration of SOA-P 5.1 to 5.2 BPEL projects is to change the project facet like so:
1. open the project properties dialog (select the project, then Alt-Enter, or from main menu click "Project->Properties")
2. enter "Facets" in the filter text box
3. the "JBoss BPEL 2.0 Facet (SOA-P v5.1 and earlier)" item should be checked - right click and "Unlock"
4. this should display all facets including "BPEL 2.0 Facet"
5. un-check "JBoss BPEL 2.0 Facet (SOA-P v5.1 and earlier)" and check "BPEL 2.0 Facet".
6. select the "Runtimes" tab and check the new "SOA-P 5.2" runtime



> Add migration path for SOA-P 5.1 to 5.2 for BPEL project facets
> ---------------------------------------------------------------
>
>                 Key: JBIDE-8533
>                 URL: https://issues.jboss.org/browse/JBIDE-8533
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: bpel
>    Affects Versions: 3.2.0.CR1
>         Environment: all
>            Reporter: Robert (Bob) Brodt
>            Assignee: Robert (Bob) Brodt
>             Fix For: 3.2.1
>
>
> SOA-P 5.2 PRD document requirement SOA-MGUP-1:
> If we decide to change the BPEL project facet ID from "jbt.bpel.facet.core" to "bpel.facet.core" (as it is defined in the eclipse.org BPEL Designer) then we will need to provide the user with some sort of migration path for SOA-P 5.1 projects.

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