[
https://jira.jboss.org/jira/browse/JBIDE-5951?page=com.atlassian.jira.plu...
]
Snjezana Peco commented on JBIDE-5951:
--------------------------------------
I can reproduce this issue using the JBT trunk.
I think that there is a problem in the PreferenceManager.initializeInstallations()
method.
It initializes jBPM runtimes placed in the state-area of the org.jboss.tools.jbpm.common
plugin which is the location for JBDS 3.0/JBT3.1.
It would be necessary to check jBPM runtimes in the state-area of the org.jbpm.gd.jpdl
plugin. A workspace created by JBDS 2.1.x contains the jbpm-instalations.xml file in the
state-area of the org.jbpm.gd.jpdl plugin, but the
PreferenceManager.initializeInstallations() method ignores it.
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.GA
Attachments: jbpm-5951.patch, 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