[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-8330) JBPM 3 process definiton wizard creates files with new (JBPM 4?) naming convention

[Koen Aers (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-8330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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.

> 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.CR1, 3.3.0.M2
>
>   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