Take care of classes from different products sharing the same name.
For now, assume that any ERP5* class has priority over non-ERP5* classes. And if conflicts can't be resolved simply, raise a loud error to force action. (This happens, for instance, with Category Tool that is initialized twice: once in CMFCategory, and a second time in ERP5 product) git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42394 20353a03-c40f-0410-a6d1-a30d3c3de9de
Showing
Please register or sign in to comment