[JBoss JIRA] Created: (GPD-12) Same JBPM project shared with each person having different JBPM installation program
1:50 a.m.
Same JBPM project shared with each person having different JBPM installation program
------------------------------------------------------------------------------------
Key: GPD-12
URL: http://jira.jboss.com/jira/browse/GPD-12
Project: JBoss jBPM GPD
Issue Type: Bug
Reporter: Tom Baeyens
Assigned To: Koen Aers
JBPM-794
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:31 a.m.
New subject: [JBoss JIRA] Updated: (GPD-12) Same JBPM project shared with each person having different JBPM installation program
[ http://jira.jboss.com/jira/browse/GPD-12?page=all ]
Koen Aers updated GPD-12:
-------------------------
Workaround Description: Make sure all uses of the project are pointing to the same
path of the jbpm in each of their systems
Environment: Eclipse, MyEclipseIDE, JBPM 3.1.2
Component/s: jpdl
Description:
To duplicate have two development machines with exactly the same versions of the software
except have the Window->Preferences->JBoss jBPM installation locations in different
places.
Have one of the people create a jBPM project, zip up that project and send it to the user
of machine 2. Then have machine 2 import that project into Eclipse.
Everything blows up. Many of the other non-related projects in the project tree also begin
displaying erratic behavior.
If both users now synchronize to have their IDEs point to the same jBPM path on each of
their machines, the project opens up fine.
was:JBPM-794
Workaround: [Workaround Exists]
Same JBPM project shared with each person having different JBPM
installation program
------------------------------------------------------------------------------------
Key: GPD-12
URL: http://jira.jboss.com/jira/browse/GPD-12
Project: JBoss jBPM GPD
Issue Type: Bug
Components: jpdl
Environment: Eclipse, MyEclipseIDE, JBPM 3.1.2
Reporter: Tom Baeyens
Assigned To: Koen Aers
To duplicate have two development machines with exactly the same versions of the software
except have the Window->Preferences->JBoss jBPM installation locations in different
places.
Have one of the people create a jBPM project, zip up that project and send it to the user
of machine 2. Then have machine 2 import that project into Eclipse.
Everything blows up. Many of the other non-related projects in the project tree also
begin displaying erratic behavior.
If both users now synchronize to have their IDEs point to the same jBPM path on each of
their machines, the project opens up fine.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:11 a.m.
New subject: [JBoss JIRA] Updated: (GPD-12) Same JBPM project shared with each person having different JBPM installation program
[ http://jira.jboss.com/jira/browse/GPD-12?page=all ]
Koen Aers updated GPD-12:
-------------------------
Fix Version/s: jBPM JPDL Designer 3.1.0.beta1
Affects Version/s: jBPM JPDL Designer 3.1.0 alpha1
Same JBPM project shared with each person having different JBPM
installation program
------------------------------------------------------------------------------------
Key: GPD-12
URL: http://jira.jboss.com/jira/browse/GPD-12
Project: JBoss jBPM GPD
Issue Type: Bug
Components: jpdl
Affects Versions: jBPM JPDL Designer 3.1.0 alpha1
Environment: Eclipse, MyEclipseIDE, JBPM 3.1.2
Reporter: Tom Baeyens
Assigned To: Koen Aers
Fix For: jBPM JPDL Designer 3.1.0.beta1
To duplicate have two development machines with exactly the same versions of the software
except have the Window->Preferences->JBoss jBPM installation locations in different
places.
Have one of the people create a jBPM project, zip up that project and send it to the user
of machine 2. Then have machine 2 import that project into Eclipse.
Everything blows up. Many of the other non-related projects in the project tree also
begin displaying erratic behavior.
If both users now synchronize to have their IDEs point to the same jBPM path on each of
their machines, the project opens up fine.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:30 a.m.
New subject: [JBoss JIRA] Updated: (GPD-12) Same JBPM project shared with each person having different JBPM installation program
[ http://jira.jboss.com/jira/browse/GPD-12?page=all ]
Koen Aers updated GPD-12:
-------------------------
Fix Version/s: jBPM JPDL Designer 3.1.0.beta2
(was: jBPM JPDL Designer 3.1.0.beta1)
Same JBPM project shared with each person having different JBPM
installation program
------------------------------------------------------------------------------------
Key: GPD-12
URL: http://jira.jboss.com/jira/browse/GPD-12
Project: JBoss jBPM GPD
Issue Type: Bug
Components: jpdl
Affects Versions: jBPM JPDL Designer 3.1.0 alpha1
Environment: Eclipse, MyEclipseIDE, JBPM 3.1.2
Reporter: Tom Baeyens
Assigned To: Koen Aers
Fix For: jBPM JPDL Designer 3.1.0.beta2
To duplicate have two development machines with exactly the same versions of the software
except have the Window->Preferences->JBoss jBPM installation locations in different
places.
Have one of the people create a jBPM project, zip up that project and send it to the user
of machine 2. Then have machine 2 import that project into Eclipse.
Everything blows up. Many of the other non-related projects in the project tree also
begin displaying erratic behavior.
If both users now synchronize to have their IDEs point to the same jBPM path on each of
their machines, the project opens up fine.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:33 a.m.
New subject: [JBoss JIRA] Updated: (GPD-12) Same JBPM project shared with each person having different JBPM installation program
[ http://jira.jboss.com/jira/browse/GPD-12?page=all ]
Koen Aers updated GPD-12:
-------------------------
Fix Version/s: jBPM JPDL Designer 3.1.0.CR
(was: jBPM JPDL Designer 3.1.0.beta2)
Same JBPM project shared with each person having different JBPM
installation program
------------------------------------------------------------------------------------
Key: GPD-12
URL: http://jira.jboss.com/jira/browse/GPD-12
Project: JBoss jBPM GPD
Issue Type: Bug
Components: jpdl
Affects Versions: jBPM JPDL Designer 3.1.0 alpha1
Environment: Eclipse, MyEclipseIDE, JBPM 3.1.2
Reporter: Tom Baeyens
Assigned To: Koen Aers
Fix For: jBPM JPDL Designer 3.1.0.CR
To duplicate have two development machines with exactly the same versions of the software
except have the Window->Preferences->JBoss jBPM installation locations in different
places.
Have one of the people create a jBPM project, zip up that project and send it to the user
of machine 2. Then have machine 2 import that project into Eclipse.
Everything blows up. Many of the other non-related projects in the project tree also
begin displaying erratic behavior.
If both users now synchronize to have their IDEs point to the same jBPM path on each of
their machines, the project opens up fine.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:51 a.m.
New subject: [JBoss JIRA] Closed: (GPD-12) Same JBPM project shared with each person having different JBPM installation program
[ http://jira.jboss.com/jira/browse/GPD-12?page=all ]
Koen Aers closed GPD-12.
------------------------
Resolution: Done
If the jBPM runtime used to define the project got deleted or is at a different location,
there may be compilation errors, but the workbench does not crash as before
Same JBPM project shared with each person having different JBPM
installation program
------------------------------------------------------------------------------------
Key: GPD-12
URL: http://jira.jboss.com/jira/browse/GPD-12
Project: JBoss jBPM GPD
Issue Type: Bug
Components: jpdl
Affects Versions: jBPM JPDL Designer 3.1.0 alpha1
Environment: Eclipse, MyEclipseIDE, JBPM 3.1.2
Reporter: Tom Baeyens
Assigned To: Koen Aers
Fix For: jBPM JPDL Designer 3.1.0.CR
To duplicate have two development machines with exactly the same versions of the software
except have the Window->Preferences->JBoss jBPM installation locations in different
places.
Have one of the people create a jBPM project, zip up that project and send it to the user
of machine 2. Then have machine 2 import that project into Eclipse.
Everything blows up. Many of the other non-related projects in the project tree also
begin displaying erratic behavior.
If both users now synchronize to have their IDEs point to the same jBPM path on each of
their machines, the project opens up fine.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6736
days inactive
6972
days old
5 comments
3 participants
participants (3)
-
Koen Aers (JIRA) -
Koen Aers (JIRA) -
Tom Baeyens (JIRA)