[
https://issues.jboss.org/browse/JBIDE-8330?page=com.atlassian.jira.plugin...
]
joe freeman commented on JBIDE-8330:
------------------------------------
A lot of applications are currently version locked against whatever JBPM 3 they are on.
But their developers want to move to Eclipse 3.6 which requires the latest tools. This
means they are required to use the new editor even though they might be running a version
of JBPM that only supports the old naming conventions. At the very least, there should be
a way to run the "New JBPM Process" wizard that generates the names under the
old naming conventions.
JBPM 3 process definiton wizard creates files with new (JBPM 4?)
naming convention
-----------------------------------------------------------------------------------
Key: JBIDE-8330
URL:
https://issues.jboss.org/browse/JBIDE-8330
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.2.0.M1, 3.2.0.CR1
Reporter: joe freeman
Assignee: Koen Aers
Fix For: 3.2.1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
We just upgraded to the 3.2.0 JBoss JBPM editing tools and the behavior has changed for
the definition creation wizard. It looks like the JBPM 3 wizard now creates files with the
JBPM 4 naming convention.It used to create files with the name gpd.xml,
processdefinition.xml and processimage.jpg. Now it creates files with
<def_name>.jpdl.xml, process.jpg and .<def_name>.gpd.xml.
This broke our file system loader code and we can't find any release notes or Jira
tickets that describe why or when this change was made. I found notes in
http://docs.jboss.org/tools/whatsnew/jbpm/jbpm-news-3.2.0.M1.html that show that this was
intentional.
I guess this could be changed to an enhancement that there should have been a property or
something to support the old format. This is a moderately large change to a product that
is essentially in maint mode.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira