[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5951) jBPM3 runtime from JBDS 2.1.1 workspace is missing when opened in 3.0.0 CR2
Koen Aers (JIRA)
jira-events at lists.jboss.org
Tue Apr 13 12:59:25 EDT 2010
[ https://jira.jboss.org/jira/browse/JBIDE-5951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12525448#action_12525448 ]
Koen Aers commented on JBIDE-5951:
----------------------------------
Snjeza, are you really sure you can reproduce this with the combination you mention? I performed the following steps and everything seemed to work as expected:
- install fresh JBDS 2.1.1
- create jBPM project in default workspace
- install fresh Eclipse Galileo JEE SR2, open (new) workspace and install JBT trunk (http://download.jboss.org/jbosstools/updates/nightly/trunk/)
- open this Eclipse/JBT instance on the workspace of JBDS 2.1.1 created earlier
Is there something I am missing?
> 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
More information about the jbosstools-issues
mailing list