On Feb 26, 2010, at 10:47 PM, Bruno Busco wrote: > This is what I am also trying to do. > Just have the possibility to *remove* all the applications but party > and content from an OFBiz installation and have it working.
I think this has to be done into two separate and independent steps: 1) framework (without party and content) independence 2) content and party independence from the other applications I think they are very different goals and I am sure that there are different people interested in one, two or both. For example, I am interested in #1 and I am less interested (I am not saying it is a bad thing, but not worth of the effort considering how I am using OFBiz) in #2. Jacopo > Please stop thinking about moving things in or out of the framework. > > The framework, if you like how it is right now, can stay there but > please let us create the possibility to remove applications according > to their declared dependency tree. > > -Bruno > > 2010/2/26 Adam Heath <[email protected]>: >> You haven't gone far enough. >> >> Stop thinking about just what you want. Or just what Bruno wants. Or >> what the guy from Timbuktu wants. >> >> Think about what we all want. >> >> Namely, the ability to pick and choose the parts of ofbiz that we want >> to make use of. >> >> Arbitrary assignments of components into parts is the wrong approach. >> Add features to lower-level components that can be extended by >> higher-level components. Add dependency references between components >> as required. >>
