7:54 a.m.
jBPM insufficient process definition renaming
---------------------------------------------
Key: JBIDE-5532
URL: https://jira.jboss.org/jira/browse/JBIDE-5532
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.1.0.CR1
Environment: Linux 64-bit, Sun JDK 1.6, JbossTools-3.1.0.v200912171816M-H185-RC1
Reporter: Jiri Peterka
Fix For: 3.1.0.GA
1. Have a jBPM project
2. Create jBPM process (lets say called "task")
3. Refactor -> Rename task package into "task2"
4. processdefinition.xml still contains
<process-definition xmlns="urn:jbpm.org:jpdl-3.2"
name="task">
It should follow new package name
--
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
2 p.m.
New subject: [JBoss JIRA] Assigned: (JBIDE-5532) jBPM insufficient process definition renaming
[
https://jira.jboss.org/jira/browse/JBIDE-5532?page=com.atlassian.jira.plu...
]
Koen Aers reassigned JBIDE-5532:
--------------------------------
Assignee: Koen Aers
jBPM insufficient process definition renaming
---------------------------------------------
Key: JBIDE-5532
URL: https://jira.jboss.org/jira/browse/JBIDE-5532
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.1.0.CR1
Environment: Linux 64-bit, Sun JDK 1.6, JbossTools-3.1.0.v200912171816M-H185-RC1
Reporter: Jiri Peterka
Assignee: Koen Aers
Fix For: 3.1.0.CR2
1. Have a jBPM project
2. Create jBPM process (lets say called "task")
3. Refactor -> Rename task package into "task2"
4. processdefinition.xml still contains
<process-definition xmlns="urn:jbpm.org:jpdl-3.2"
name="task">
It should follow new package name
--
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
2:02 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-5532) jBPM insufficient process definition renaming
[
https://jira.jboss.org/jira/browse/JBIDE-5532?page=com.atlassian.jira.plu...
]
Koen Aers resolved JBIDE-5532.
------------------------------
Resolution: Rejected
The package is only for convenience purposes. There is no way to know if a name change of
the package relates to the processes that it contains. Packages can contain multiple
process definition files (cfr. Seam). Also, there is no way to determine if the package
relates to processes, to java content or to both.
jBPM insufficient process definition renaming
---------------------------------------------
Key: JBIDE-5532
URL: https://jira.jboss.org/jira/browse/JBIDE-5532
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.1.0.CR1
Environment: Linux 64-bit, Sun JDK 1.6, JbossTools-3.1.0.v200912171816M-H185-RC1
Reporter: Jiri Peterka
Assignee: Koen Aers
Fix For: 3.1.0.CR2
1. Have a jBPM project
2. Create jBPM process (lets say called "task")
3. Refactor -> Rename task package into "task2"
4. processdefinition.xml still contains
<process-definition xmlns="urn:jbpm.org:jpdl-3.2"
name="task">
It should follow new package name
--
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
11:11 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-5532) jBPM insufficient process definition renaming
[
https://jira.jboss.org/jira/browse/JBIDE-5532?page=com.atlassian.jira.plu...
]
Aliaksey Nis closed JBIDE-5532.
-------------------------------
Rejected issue closed.
jBPM insufficient process definition renaming
---------------------------------------------
Key: JBIDE-5532
URL: https://jira.jboss.org/jira/browse/JBIDE-5532
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.1.0.CR1
Environment: Linux 64-bit, Sun JDK 1.6, JbossTools-3.1.0.v200912171816M-H185-RC1
Reporter: Jiri Peterka
Assignee: Koen Aers
Fix For: 3.1.0.CR2
1. Have a jBPM project
2. Create jBPM process (lets say called "task")
3. Refactor -> Rename task package into "task2"
4. processdefinition.xml still contains
<process-definition xmlns="urn:jbpm.org:jpdl-3.2"
name="task">
It should follow new package name
--
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
9:06 a.m.
New subject: [JBoss JIRA] Reopened: (JBIDE-5532) jBPM insufficient process definition renaming
[
https://jira.jboss.org/jira/browse/JBIDE-5532?page=com.atlassian.jira.plu...
]
Jiri Peterka reopened JBIDE-5532:
---------------------------------
The package (for example process) from JBT point of view can IMHO contain only one process
definition, because it requires gpd.xml file and it always creates processimage.jpg, so
process definition name could reflects process folder when renamed. I see no way howto
create more process definitions in the same folder that would work with JBT.
jBPM insufficient process definition renaming
---------------------------------------------
Key: JBIDE-5532
URL: https://jira.jboss.org/jira/browse/JBIDE-5532
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.1.0.CR1
Environment: Linux 64-bit, Sun JDK 1.6, JbossTools-3.1.0.v200912171816M-H185-RC1
Reporter: Jiri Peterka
Assignee: Koen Aers
Fix For: 3.1.0.CR2
1. Have a jBPM project
2. Create jBPM process (lets say called "task")
3. Refactor -> Rename task package into "task2"
4. processdefinition.xml still contains
<process-definition xmlns="urn:jbpm.org:jpdl-3.2"
name="task">
It should follow new package name
--
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
9:20 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-5532) jBPM insufficient process definition renaming
[
https://jira.jboss.org/jira/browse/JBIDE-5532?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen resolved JBIDE-5532.
----------------------------------------
Resolution: Rejected
Not being able to have more than one process in a package is a separate bug than
refactoring - please create separate issue for that. Thanks.
The task name can afaik I know be named whatever you want.
jBPM insufficient process definition renaming
---------------------------------------------
Key: JBIDE-5532
URL: https://jira.jboss.org/jira/browse/JBIDE-5532
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.1.0.CR1
Environment: Linux 64-bit, Sun JDK 1.6, JbossTools-3.1.0.v200912171816M-H185-RC1
Reporter: Jiri Peterka
Assignee: Koen Aers
Fix For: 3.1.0.CR2
1. Have a jBPM project
2. Create jBPM process (lets say called "task")
3. Refactor -> Rename task package into "task2"
4. processdefinition.xml still contains
<process-definition xmlns="urn:jbpm.org:jpdl-3.2"
name="task">
It should follow new package name
--
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
9:56 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5532) jBPM insufficient process definition renaming
[
https://jira.jboss.org/jira/browse/JBIDE-5532?page=com.atlassian.jira.plu...
]
Jiri Peterka commented on JBIDE-5532:
-------------------------------------
Currently as I know it's constructed for one process definition for one folder becuase
there is only one one gpd.xml for all process definitions. So I'm not sure ir this is
a bug, it's simply designed for one process definition. Purpose of this bug was to
allow complex refactoring-renaming of the process together with folder name. Anyway I
created Feature Request JIRA for support more porcesses in one folder
(https://jira.jboss.org/jira/browse/JBIDE-5911).
jBPM insufficient process definition renaming
---------------------------------------------
Key: JBIDE-5532
URL: https://jira.jboss.org/jira/browse/JBIDE-5532
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.1.0.CR1
Environment: Linux 64-bit, Sun JDK 1.6, JbossTools-3.1.0.v200912171816M-H185-RC1
Reporter: Jiri Peterka
Assignee: Koen Aers
Fix For: 3.1.0.CR2
1. Have a jBPM project
2. Create jBPM process (lets say called "task")
3. Refactor -> Rename task package into "task2"
4. processdefinition.xml still contains
<process-definition xmlns="urn:jbpm.org:jpdl-3.2"
name="task">
It should follow new package name
--
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
7:55 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5532) jBPM insufficient process definition renaming
[
https://jira.jboss.org/jira/browse/JBIDE-5532?page=com.atlassian.jira.plu...
]
Jiri Peterka commented on JBIDE-5532:
-------------------------------------
Max, is that really ok for you, that when processdefinition.xml is renamed it removes all
package from filesystem? My opinion is that this shoud be fixed (disable rename menu item
or not to change file name when renamed).
jBPM insufficient process definition renaming
---------------------------------------------
Key: JBIDE-5532
URL: https://jira.jboss.org/jira/browse/JBIDE-5532
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.1.0.CR1
Environment: Linux 64-bit, Sun JDK 1.6, JbossTools-3.1.0.v200912171816M-H185-RC1
Reporter: Jiri Peterka
Assignee: Koen Aers
Fix For: 3.1.0.CR2
1. Have a jBPM project
2. Create jBPM process (lets say called "task")
3. Refactor -> Rename task package into "task2"
4. processdefinition.xml still contains
<process-definition xmlns="urn:jbpm.org:jpdl-3.2"
name="task">
It should follow new package name
--
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
2:04 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-5532) jBPM insufficient process definition renaming
[
https://jira.jboss.org/jira/browse/JBIDE-5532?page=com.atlassian.jira.plu...
]
Jiri Peterka closed JBIDE-5532.
-------------------------------
Forgot my previous comment, this is solved in JBIDE-5910, closing.
jBPM insufficient process definition renaming
---------------------------------------------
Key: JBIDE-5532
URL: https://jira.jboss.org/jira/browse/JBIDE-5532
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.1.0.CR1
Environment: Linux 64-bit, Sun JDK 1.6, JbossTools-3.1.0.v200912171816M-H185-RC1
Reporter: Jiri Peterka
Assignee: Koen Aers
Fix For: 3.1.0.CR2
1. Have a jBPM project
2. Create jBPM process (lets say called "task")
3. Refactor -> Rename task package into "task2"
4. processdefinition.xml still contains
<process-definition xmlns="urn:jbpm.org:jpdl-3.2"
name="task">
It should follow new package name
--
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
2:04 a.m.
New subject: [JBoss JIRA] Assigned: (JBIDE-5532) jBPM insufficient process definition renaming
[
https://jira.jboss.org/jira/browse/JBIDE-5532?page=com.atlassian.jira.plu...
]
Jiri Peterka reassigned JBIDE-5532:
-----------------------------------
Assignee: Jiri Peterka (was: Koen Aers)
jBPM insufficient process definition renaming
---------------------------------------------
Key: JBIDE-5532
URL: https://jira.jboss.org/jira/browse/JBIDE-5532
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.1.0.CR1
Environment: Linux 64-bit, Sun JDK 1.6, JbossTools-3.1.0.v200912171816M-H185-RC1
Reporter: Jiri Peterka
Assignee: Jiri Peterka
Fix For: 3.1.0.CR2
1. Have a jBPM project
2. Create jBPM process (lets say called "task")
3. Refactor -> Rename task package into "task2"
4. processdefinition.xml still contains
<process-definition xmlns="urn:jbpm.org:jpdl-3.2"
name="task">
It should follow new package name
--
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
5897
days inactive
5967
days old
jbosstools-issues@lists.jboss.org
9 comments
4 participants
participants (4)
-
Aliaksey Nis (JIRA) -
Jiri Peterka (JIRA)
-
Koen Aers (JIRA)
-
Max Rydahl Andersen (JIRA)