[ https://issues.jboss.org/browse/JBIDE-8330?page=com.atlassian.jira.plugin... ] joe freeman updated JBIDE-8330: ------------------------------- Description: 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. was: 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. Was this change on purpose -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8330?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-8330: -------------------------------------------- what "file system loader code" ? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8330?page=com.atlassian.jira.plugin... ] joe freeman commented on JBIDE-8330: ------------------------------------ I knew I shouldn't have put that in there! We currently load all processdefinition.xml files on the classpath and not from a DB. Now we need to load against other patterns since there doesn't seem to be a way to create definitions with the old naming conventions. My main point with this Jira is that someone changed the naming conventions for a "mature" tool without anything obvious showing up in the release notes Jira list. This change along with the one mentioned in JBIDE-8331 have had a real impact on us. I eventually found comments his change in "what's new" but I had to do a lot of searching before I found it. Our current workaround is to copy/paste existing definitions in the file manager and then edit/delete/insert in Eclipse. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ 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. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8330?page=com.atlassian.jira.plugin... ] Koen Aers resolved JBIDE-8330. ------------------------------ Fix Version/s: 3.3.0.M2 (was: 3.3.0.CR1) Resolution: Won't Fix Actually the old naming conventions are still supported. The wizard does not create this file structure anymore by default but you can very well create it manually and the editor will still work as before. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira