How do you use your Apache Camel?

The Apache Camel project has been growing by leaps and bounds lately it seems. Much of this growth has been driven by a vibrant community (many thanks to all users! :) ). Its typically hard though to know what kind of applications Camel is being used in. We don't have much visibility into the cool stuff people are doing with Camel. In particular, in would be nice to know what other applications are being used with Camel... eg. CMSs, DBs, ESBs, App Servers, web frameworks, other frameworks, etc etc

I've started a thread here trying to capture how folks are using Camel. Please, if you're a user of Camel, take a minute to share how it is being used on the thread or here. This will only help us make Camel better and more useful in the future. No confidential info allowed, of course ;)

Creating Apache Camel projects with m2eclipse

I just noticed today that Apache Camel shows up by default in the m2eclipse New Maven Project dialog. No extra fooling around is required anymore. Very cool!


This is by far the easiest way to get started with Apache Camel - you don't even have to leave your IDE.

Apache Camel 1.5.0 Released!

Several months and 266 fixes later (a new record!), the Apache Camel team is proud to present version 1.5.0!

Go ahead, take a look at the release notes and grab it here. Its still pretty fresh so it may take a few hours before the release propagates to all Apache download mirrors (try here otherwise).

Repeatable Maven Builds

A typical problem folks have with Maven seems to be getting repeatable builds. If you've encountered this, you know the pain: an older release needs to be built but now fails with the dreaded "Failed to resolve artifact" error. You can't really depend on most Maven repos to be there indefinitely. I'm sure repos like http://repo1.maven.org are pretty safe but AFAIK the maintainers are under no legal obligation to keep around the artifacts forever. You most likely DO have obligations to customers and thus need to ensure builds are repeatable.

You get repeatability for free when you use a repository manager like Nexus - it keeps downloaded artifacts around forever by default. If you don't want to use a repository manager, you're going to have to save those artifacts some other (manual) way. One approach would be to just tar up your local m2 repo after each release and store it somewhere safe (like in SVN). Of course, since local repos tend to get huge over time, you should always start from an empty local repo before a release.

Hope this helps.

Why drop Maven?

Recently I've noticed projects dropping Maven in favour of some other build tool... Apache Qpid comes to mind in this case. I'm wondering, is there a real good technical reason that folks do not like Maven? It has its quirks... but really, what tool doesn't? I've been using it for years now and like it better that any other build tool out there.

Nexus indices added for FUSE

I've added Nexus repository indices for the FUSE Maven repositories. You can find instructions on how to add these to your m2eclipse installation here.

Why should you care? Well, among many other things, this enables you:

1. Create new projects based on Camel archetypes
2. Search for classes in all FUSE artifacts
3. Add FUSE dependencies to your project's POM

Nexus config for Apache Camel

Some folks have been having issues getting all the Maven repositories set up properly in Nexus for Apache Camel. Here's my working Nexus config and settings.xml - hope it helps!

Nexus config (admittedly polluted with repos from other projects...)

settings.xml

I found my Nexus config in /opt/sonatype-work/nexus/conf. I'm not sure what happens when you copy in a new Nexus config file so you should probably make a copy of the sonatype-work directory first :)