]
Robert (Bob) Brodt updated JBPM-3108:
-------------------------------------
Attachment: fix.patch
patch that adds content describer to editor plug-in
Change file extension from .bpmn2 to .bpmn and use content
descriptors to associate with correct editor
-------------------------------------------------------------------------------------------------------
Key: JBPM-3108
URL:
https://issues.jboss.org/browse/JBPM-3108
Project: jBPM
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Eclipse
Reporter: Gary Brown
Assignee: Kris Verlaenen
Fix For: jBPM 5.x
Attachments: fix.patch
Currently the BPMN2 editor creates files with extension .bpmn2.
Although the spec does not explicitly indicate what file extension should be used, the
examples distributed by the OMG use the .bpmn extension.
The issue is that currently this would conflict with users of the existing BPMN1 Eclipse
editor.
Idea from Bob Brodt is to use the same extension, but both editors use the
ContentDescriptor approach to determine which editor should be used. See
http://community.jboss.org/wiki/EclipseFileContentTypes
--
This message is automatically generated by JIRA.
For more information on JIRA, see: