We follow the normal software model where we branch our source code and all related artifacts for each release. We also do this when we have a special project. This means that awlays have two or more active development branches. We keep all of our process definition XML files in our repository and bundle them with our application in the ear/war file. We're trying to figure out how we are going to "diff" and "merge" the BPM files between the various branches.
We have 60+ BPM flows each of which consists of 3 components. We really need a way to merge the processdefinition.xml file. One problem there is that the designer often dies if you manually edit an xml file and any type of merge would be an xml file. The builder needs to be more robust about displaying what it can when it gets confused, even if it tosses the rest of the data. It would seem that we would really like to merge the layouts also but I'm not sure what that means. image.jpg files should probably be tossed and completely regenerated. In an ideal world, we'd do this with a graphical tool. Maybe where the two merging diagrams both show up in the builder in some color coded fashion. How do others handle version management of BPM files? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109390#4109390 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109390 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
