Hi Antonio, In my opinion the most important thing we can do now is to find out why happens even to experienced developers and solve it once and for all. Is the system too complex? Is the process too delicate? Is the process fine but difficult to follow? Does it require a discipline that is not realistic? If the process fine, easy to follow, but are we just lazy?
> One possible solution to this problem would be to automatically execute > the Synchronize Terminology process just before the export.database > task. This would mean that developers wouldn't need to remember to do > it, but it would add about 30 secs to the overall duration of the > export.database process. We would need to carefully consider if this is > worth it. If this fixes most of the inconsistencies then we'll have to consider it. Some developers may argue that adding a delay to every database export is unacceptable. And this concern is understandable. What do the rest think about this? Do you have any alternative idea? Thank you for your answer and for your suggestion to fix this. Juan Pablo ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Openbravo-development mailing list Openbravo-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbravo-development
