camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] [Updated] (CAMEL-3886) Reduce compiler warnings when imported into eclipse
Date Wed, 20 Apr 2011 16:38:05 GMT


Daniel Kulp updated CAMEL-3886:

    Attachment: warnings.patch

I've attached a patch that gets the count down to 24.   

For the most part, what I did includes:

1) If the code that has warnings is in a SNIPPET tag, I left the code alone so the website
docs can remain as is, but added @SuppressWarnings annotations outside the block.

2) In most other places, if I could "fix" the code by using information documented on the
web site, I did.

3) I added a couple methods to ProxyBuilder/Helper to simplify and clear up the single Class
case which generates a bunch of warnings.

The remaining warning are all related to the deprecation of "handled" on TryDefintion and
DefaultErrorHandlerBuilder.   Will follow up on list about those.

> Reduce compiler warnings when imported into eclipse
> ---------------------------------------------------
>                 Key: CAMEL-3886
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core, camel-cxf, camel-spring
>            Reporter: Daniel Kulp
>         Attachments: warnings.patch
> When I import/open camel-cxf in eclipse and it automatically opens the the projects it
depends on, Eclipse displays about 150 compiler warnings that should be cleaned up.

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message