On 20 July 2010 16:51, Ron Smith <ron.sm...@valkyresoftware.com> wrote: > 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?
There kinda already is :). camel-core.jar is the core :). That comes with a bunch of components/endpoints. Everything else is pretty much a new kind of endpoint/component (or language mostly). > And, if we go that route, how do you manage the > dependencies of each of the add-ins? Each add-on has its dependencies clearly described in a pom.xml and in the maven reports. > 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. We've gotten out of the habbit of generating the maven site - but it describes the dependencies of each module in camel nicely... http://camel.apache.org/maven/camel-2.2.0/camel-core/dependencies.html you can also look inside the jar to see the pom.xml which describes them too. You can also use other repos and websites too... http://mvnrepository.com/artifact/org.apache.camel/camel-jms e.g. http://mvnrepository.com/artifact/org.apache.camel/camel-jms/2.4.0 -- James ------- http://macstrac.blogspot.com/ Open Source Integration http://fusesource.com/
