Serge Knystautas wrote:
On 4/20/06, Steve Brewin <[EMAIL PROTECTED]> wrote:
Serge Knystautas wrote:
Guys,
I was going to commit this, but wanted to run it by you just since it
introduces another dependency.
Ugh! Surely this is an optional feature. If people want to use it only then
should they need to add the dependencies.
If and when we move to OSGi, choosing to incorporate a feature will
automagically ensure that the dependencies are present. Until then an
optional mailet needs to be manually supplied with its dependents.
Does a 144k jar really warrant an "ugh"? Cocoon has 29.4m of optional
jars that it bundles.
Unfortunately the size of a binary download is often taken as a
synonymous of its runtime 'lightweight'ness.
In past I thought about bundling SMIME stuff in a different package to
reduce James basic size furthermore.
IMHO if we want to add features that needs thirdparty jars we could then
distribute 2 different James versions: basic and full.
I know this is only marketing things but an meaningless "download size"
often has a big impact on the spreading of the product.
If OSGi will dynamically download jars on demand, then sounds pretty
cool. I don't know much about it.
Not sure, but I don't think that OSGi itself automatically downloads
packages. Maybe there are third party OSGi services that automatically
do that.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
