Today I stumbled about Clirr [1]. "Clirr is a tool that checks Java libraries for binary and source compatibility with older releases." May this is helpful for us because we back port multiple changes into older releases, most in an automated way... It's possible to break the build if a change introduce binary/source incompatibilities.
Should we add it into the Camel build? May with its own profile? [1] http://clirr.sourceforge.net/ Best, Christian