[ https://jira.jboss.org/browse/JBDS-1442?page=com.atlassian.jira.plugin.sy... ] Brian Fitzpatrick reassigned JBDS-1442: --------------------------------------- Assignee: Koen Aers Koen, can you take a look at this? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1442?page=com.atlassian.jira.plugin.... ] Koen Aers updated JBDS-1442: ---------------------------- Fix Version/s: 4.0.0.CR1 (was: 4.0.0.Beta2) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1442?page=com.atlassian.jira.plugin.... ] Koen Aers resolved JBDS-1442. ----------------------------- Resolution: Done Fixed and Verified in JBDS-4.0.0.Beta2 and JBT-3.2.0.Beta2 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1442?page=com.atlassian.jira.plugin.... ] Pavol Srna commented on JBDS-1442: ---------------------------------- This issue is still reproducible. In order to reproduce go through these steps: 1) Create jBPM project in JBDS 3.0.1.GA. The wizard will prompt for JBPM runtime. I used JBPM runtime from SOA 5.1.0.ER6 2) Open JBDS 4.0.0.CR1 with clean workspace 3) Import jBPM project from JBDS 3 into JBDS 4.0.0.CR1 workspace (File -> Import... -> General -> Existing Projects into Workspace) Select "Copy projects into workspace" checkbox in the import wizard. It is not possible to get rid of errors. I tried "Clean", "Close and Open project", "Refresh". I also noticed that the jbpm runtime name (see Window -> Preferences -> Jboss jBPM -> Runtime Locations) has changed after import. The problem is still there even if I change the jBPM runtime name as it was in the JBDS 3.0.1.GA workspace. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1442?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick updated JBDS-1442: ------------------------------------ Original Estimate: 0 minutes Remaining Estimate: 0 minutes Fix Version/s: 4.0.0.CR2 (was: 4.0.0.CR1) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBDS-1442?page=com.atlassian.jira.plugin.... ] Koen Aers resolved JBDS-1442. ----------------------------- Resolution: Partially Completed If the runtime is defined (with a correct name) before the project is imported, there is no problem at all. If the project is imported before the runtime is defined, the problem will go away after defining the runtime (again with a correct name) and then restarting Eclipse. It seems not worth going deeper in this issue to try to remove this last inconvenience completely as there is a simple workaround that only needs to be performed one time. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira