You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@camel.apache.org by Christian Müller <ch...@gmail.com> on 2012/01/25 00:34:48 UTC

Clirr - Checks for binary and source compatibility with older releases

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

Clirr - Checks for binary and source compatibility with older releases

Posted by Richard Kettelerij <ri...@gmail.com>.

Whilst I can't comment on the tool itself (haven't used it before), do note
the project is inactive. There hasn't been a release for over 6 years...

Regards,
Richard

On Wednesday, January 25, 2012, Christian Müller <
christian.mueller@gmail.com> wrote:
> 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
>

-- 
Sent from Gmail Mobile