Pablo Sarobe wrote: > I agree with Isma's approach and for sure I wouldn't allow to disable > the validation. The validation should be a must
Hi, we already have some validation in place on export and disabling it is already possible (and useful sometimes). You don't want to block a commit/MP just because the validation code itself has a bug... The case of people disabling it and then forgetting some mandatory tasks (like synchronize terminology) can be easily caught in process... One extra note: Synchronize terminology is only one step of several which might be necessary (depending on what you develop)... change in whitespace in src-db or forgetting to compile.complete once with core in development (to update ad_textinterfaces...) are also possible problems (if they are forgotten) and won't be solved by this.. I am still in favor of a educate/talk to people or give an incentive to make it right, like: 1 Euro into a box for each violation and we all get some tortillas if we have enough.. Cheers, Stefan ------------------------------------------------------------------------------ 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
