> You need to update core and the affected modules together in one > batch, > as the following two combinations of: > > a.) old core - new module > b.) new core - old module > > will fail to compile. > The combination a.) has been excluded by specifying proper > dependencies > but for b.) nothing can be done via dependencies so it will fail if > someone only updates core and not the modules.
Is it true that nothing can be done about b)? Maybe, if we had renamed the core 2.51 with that update, the effect could have been prevented. Can you confirm my hypothesis? In any case, I am sure there are ways to solve this problem. Let's see if we can find one that we can easily implement. ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Openbravo-development mailing list Openbravo-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbravo-development
