I hadn't thought about it that way, James, but does that mean there needs to be some distinction between what is "core" functionality and what is "add-in" functionality? And, if we go that route, how do you manage the dependencies of each of the add-ins? I think Claus is on the right track by separating out the jars for spring and Java 5, etc into subdirectories under the lib. That way, they will be there if they are needed and the requirements becomes more a little more clear. It still doesn't specify which camel jars depend on which spring or other jars but, if someone (like myself) chooses (or is forced) not to use maven, then it is on their (my) head to resolve those dependencies. At least I have the definitive set of resources available to do the resolution.
On Tue, Jul 20, 2010 at 10:03 AM, James Strachan <james.strac...@gmail.com>wrote: > On 20 July 2010 14:21, Ron Smith <ron.sm...@valkyresoftware.com> wrote: > > I am really not trying to be difficult, I promise (imagine if I were :-) > ) > > > > So, there are Spring JARs that are now required for camel 2.4.0 but are > not > > included in the binary distribution because the new version of Sping, has > > additional dependencies that only get sorted out if you choose to use > maven? > > > > I don't mean to start another thread complaining about the dependency on > > maven (though I tend to agree), I see there are already plenty of those. > My > > intent is to suggest that if Camel is intended to be its own framework > and > > not just a bag on the side of Spring, the binary distribution of Camel > > should contain the jars required to run Camel and not just enough to get > it > > to compile. > > FWIW Camel itself isn't dependent on Spring - you don't need spring at > all to run Camel and lots of its components. > > But there are quite a few components which do depend on Spring (such > as camel-jms) so its probably worth including Spring as well - even > though its not required for Camel per se. > > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://fusesource.com/ >
