[
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.
jBPM project import from JBDS 3.0.1.GA into JBDS.4.0.0.Beta2
workspace doesn't work
-----------------------------------------------------------------------------------
Key: JBDS-1442
URL:
https://issues.jboss.org/browse/JBDS-1442
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: jBPM
Affects Versions: 4.0.0.Beta2
Environment: JBDS 3.0.1.GA, JBDS 4.0.0Beta2
(jbdevstudio-eap-linux-gtk-4.0.0.v201012021737R-H23-Beta2), jboss-soa-p.5.0.0, linux32bit
Reporter: Pavol Srna
Assignee: Koen Aers
Priority: Blocker
Fix For: 4.0.0.CR2
Attachments: JBDS-1442.patch
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The jBPM Runtime is corrupted after project import and it is not possible to correct it.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira