We use a large number of flows to better isolate the changes and reduce the risk of collision with the 10 or so process developers. We could model it with fewer flows but we'd have less process re-use and more modeling bottlenecks. The other problem is that the editor gets unwieldy with over a certain number of boxes. We have one flow with 20+ boxes and that seems to be about the max. (I meant to say that our flows have as few as 3 boxes) We use Perforce, basic QA and common sense for that part.
The hard part is branch management. A real app, once in production, typically runs with 3 branches, "production support", "next release" and "future work". The branches are often run by different managers and different schedules. We're trying to figure out the best way to manage the merge and sync process given the fact that each flow consists of 3 components, model, layout and image. Most of our merging and diff tools do a very poor job on XML files. Plain text (java) files are easier to merge because you can bring broken code into the Java source editor and use Eclipse's syntax tools to help put it back together. XML tools are significantly less helpful. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109690#4109690 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109690 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
