camel-core doesn't have any third part dependencies (only slf4j).
But the whole camel project may have 450M third part dependency as it
out of our control.
I think camel-core has some built-in components and EIP implementation
helps user to start up a simple EIP journey by using a 1.6M tool without
any pain, that is amazing impression of Camel.
I'm still OK if it is less then 3M.
On 9/1/11 4:15 AM, Donald Whytock wrote:
On Wed, Aug 31, 2011 at 3:26 PM, Claus Ibsen<claus.ib...@gmail.com> wrote:
The core is 1.6mb which is not bloated. In fact with the core you can
do really a lot with Camel, which impress
a lot of people, and help make the project a success it is today.
In all fairness, 1.6 mb is bigger than the entire Felix framework,
including the documentation. The camel-core jar represents two-thirds
of the volume of my deployed Felix OSGI application.
Yes, the core does a lot, but how many people genuinely use all the
features and built-in components? Not that I'm necessarily advocating
splitting it into all separate modules, since it would probably take
up more space that way, what with the extra manifests and activators
and all.
But still, even if not "bloated", I might call it "non-trivially sized".
Don
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
