That's the approach I tried when I ran into dependency problems. This
then worried me that if I did fix the dependency problem I found, what
other dependency issues would I run into later down the line?
A developer learning ofbiz doesn't need to think about component
dependencies on top of learning the framework!
I was thinking about your comment of leaving the components in place
even though they are not used. Does leaving unused components in place
have a performance impact on ofbiz? Do those components consume memory?
- they are certainly using disk space. Some of the components for
example BIRT consume a fair amount of space.
Can you imagine if Eclipse worked by making you install every plugin
available even if you don't use it? The performance impact on eclipse
wouldn't be too bad though because eclipse lazily loads plugins when
they are first used.
Abdullah Shaikh wrote:
I am not sure, I haven't tried this, but could commenting the not required
components from component-load.xml file have helped ?
On Fri, Nov 13, 2009 at 3:40 PM, Christopher Snow <
[email protected]> wrote:
When I tried to remove the unwanted components, I can into dependency
problems. A modular approach to using the components such as maven would
stop the developer having to manually work out dependencies to remove
components.
Leaving the unwanted components in place even though they don't get used
makes DBA's and support people twitchy, asking questions like "why are all
those tables created even though they aren't used?"
