Hi David, Neogia addons-manager isn't only a series of patches. The dependence system allows to create addons with orientation : * technical (ex : multi-delegator, pdf-view-handler) : improvement on ofbiz technical framework * functional (ex : oisg-status, company) : imporement on ofbiz functional framework * end-user application (ex : naccounting, nmanufacturing) : add standard OFBiz components
In general, we have a end-user appication that content dependency on functional and technical addons. If two addons change the same code, there is a architectural problem, we need create a new addon who manage the conflict reason. If two addons change/add code on the same area, the addon-manager detect and resolve the problem. The actual OFBiz components system is good but when you need improve the functional system, is difficult to submit your enhancement, need test on your components, after update on OFBiz framework and try to explain it for validation. In most case, if you aren't a commiter you take your functional enhancement in your component and it's not integrate in OFBiz functionnal and can't use for other compenent without create dependency in hot-deploy or specialpurpose. With addons, all functional enhancement are put in specific addon and it use for many end-user addon. After it's more easier to create a jira for integrate in OFBiz framework (after we juste remove addon dependency ;) ) OFBiz Why not become the first modular integrated ERP with a library addition to management as a debian (we have a functioning distribution management company;)) Nicolas -- View this message in context: http://n4.nabble.com/Question-about-add-ons-tp1749458p1750801.html Sent from the OFBiz - User mailing list archive at Nabble.com.
