Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-bpmn2.dev] Points to clearify
Hi Reiner,

I agree with you on (1) - see https://bugs.eclipse.org/bugs/show_bug.cgi?id=319957, which has a similar intention (I'll add the line ending problem there).

Regarding the package names (3): I'd prefer that we use bpmn2. Antoine mentioned that he wants to avoid having to rename them with each new specification version, but I think that we can keep bpmn2 at least until BPMN3 comes out - which presumably would require a new project and would not be handled within the BPMN2 project. Having the version number in the package name (and everywhere else) will allow clearer separation between different BPMN versions, that is, between 1 and 2 (e.g. no conflicts with the BPMN diagram editor).

@(4): I'm in favor of o.e.dd.di/dc.

Thanks,
Henning

2010/7/15 Hille-Doering, Reiner <reiner.hille-doering@xxxxxxx>
Hi all,
I see that you all work and commit improvement – great.
However I see some issues that we should clearify:
  1. I see that after Antoin’s last commit all committed files have UNIX line ending (0x0A). Before they had Windows ending (0x0D0A). This is a problem, because diffing is complicated. I don’t have problems with Unix line endings, but we should do it consistently.
  2. Antoin’s commit killed some of my “@generated NOT” methods. At least in “Bpmn2ResourceFactoryImpl” my handwritten code is lost. This is really bad, because without the changes the BPMN XML import and save will not work. I would ask you to avoid deleting files before regeneration or before commit to check the diffs carefully.
  3. I would like to know if we want to rename the plugins, packages and class name prefixes back from “bpmn2” to “bpmn”. I can do it, but it would be good to have no parallel central commits, because merging such change is almost impossible. Please vote.
  4. The same questions applies for the package prefix for the “di” and “dc” packages to include “dd”.
 
Thanks and regards,
Reiner.
 
 
 

_______________________________________________
mdt-bpmn2.dev mailing list
mdt-bpmn2.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-bpmn2.dev


Back to the top