[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5951) jBPM3 runtime from JBDS 2.1.1 workspace is missing when opened in 3.0.0 CR2

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-5951:
--------------------------------------------

crap. so old ones were created in org.jbpm.gd.jpdl but now they are created in org.jbpm.common ...

About the cyclic relationship then you don't need to have access to the plugin, just the string id. 
Wouldn't the best to actually read the runtimes with both the old and new id ? 

Or simply use the old id for full backwards compatibility ?



> jBPM3 runtime from JBDS 2.1.1  workspace is missing when opened in 3.0.0 CR2
> ----------------------------------------------------------------------------
>
>                 Key: JBIDE-5951
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5951
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: jbpm
>    Affects Versions: 3.1.0.CR2
>         Environment: JBDS 3.0.0 CR2 184, Linux 32
>            Reporter: Jiri Peterka
>            Assignee: Koen Aers
>            Priority: Critical
>             Fix For: 3.1.0.CR3, 3.1.0.GA
>
>         Attachments: ws-3-missing-jbpm-iibs.png
>
>
> When workspace with jbpm3 project created in JBDS 2.1.1 GA is opened in JBDS 3.0.0 CR2, there is missin jbpm3 runtime setting.
> Assumption is jbpm3 runtime setting set in 2.1.1 should be available when opened in 3.0.0. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira