[ https://jira.jboss.org/jira/browse/JBIDE-5951?page=com.atlassian.jira.plu... ] Jiri Peterka updated JBIDE-5951: -------------------------------- Attachment: ws-3-missing-jbpm-iibs.png -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5951?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-5951: -------------------------------------------- Jiri - can you show the preferences for your jbpm3 runtimes configuration ? -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5951?page=com.atlassian.jira.plu... ] Jiri Peterka commented on JBIDE-5951: ------------------------------------- Max - jbpm3 runtime configuration is empty in Preferences in JBDS 3.0.0, so it's some jbpm3 setting incompatibility -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5951?page=com.atlassian.jira.plu... ] 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 ? -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5951?page=com.atlassian.jira.plu... ] Koen Aers updated JBIDE-5951: ----------------------------- Attachment: jbpm-5951.patch applying this patch solves the problem -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5951?page=com.atlassian.jira.plu... ] Jiri Peterka reopened JBIDE-5951: --------------------------------- Koen, doesn't work for me on JBDS 3.0.0 GA #50. -- 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

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

[ https://jira.jboss.org/jira/browse/JBIDE-5951?page=com.atlassian.jira.plu... ] Snjezana Peco commented on JBIDE-5951: -------------------------------------- JBDS 2.1.1 and JBoss Tools trunk -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5951?page=com.atlassian.jira.plu... ] Snjezana Peco commented on JBIDE-5951: -------------------------------------- I have done the following: - installed fresh JBDS 2.1.1 - created the "jbpm" jBPM runtime jBPM Runtime exists in Window>Preferences>JBoss jBPM>Runtime Locations - checked <WORKSPACE_JBDS_211>\.metadata\.plugins\org.jbpm.gd.jpdl\jbpm-installations.xml The file contains the previously created jBMP runtime. - started the JBoss Tools trunk in the PDE Runtime on <WORKSPACE_JBDS_211> workspace - selected Window>Preferences>JBoss jBPM>Runtime Locations The "jbpm" jBPM runtime doesn't exist. o.j.t.jbpm.common creates an empty <WORKSPACE_JBDS_211>\.metadata\.plugins\org.jboss.tools.jbpm.common\jbpm-installations.xml and checks if there is the "jbpm" runtime at this location. The <WORKSPACE_JBDS_211>\.metadata\.plugins\org.jbpm.gd.jpdl\jbpm-installations.xml file created by JBDS 2.1.1 is ignored. I have also checked the o.j.t.jbpm.common source code. The PreferenceManager class doesn't check the <WORKSPACE_JBDS_211>\.metadata\.plugins\org.jbpm.gd.jpdl\jbpm-installations.xml file -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5951?page=com.atlassian.jira.plu... ] Koen Aers updated JBIDE-5951: ----------------------------- Attachment: jbpm-5951bis.patch I solved the problem by contributing a org.eclipse.ui.startup extension. I couldn't find any other way to copy the runtime definitions if no jBPM project is defined in the workspace. I applied the patch to trunk and the 3.1.x branch. -- 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

[ https://jira.jboss.org/browse/JBIDE-5951?page=com.atlassian.jira.plugin.s... ] Jiri Peterka commented on JBIDE-5951: ------------------------------------- Koen, pls change fix version to reflect real situation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-5951?page=com.atlassian.jira.plugin.s... ] Jiri Peterka closed JBIDE-5951. ------------------------------- Assignee: Jiri Peterka (was: Koen Aers) Verified in JBDS 3.0.1.v201006010437R-H98-GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira