hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-2364) Ignore Deprecations during build
Date Tue, 23 Mar 2010 03:59:27 GMT

     [ https://issues.apache.org/jira/browse/HBASE-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack resolved HBASE-2364.
--------------------------

       Resolution: Fixed
    Fix Version/s: 0.21.0
         Assignee: Paul Smith
     Hadoop Flags: [Reviewed]

Committed to TRUNK though I'm a little worried this one-line patch will destabilize the whole
code base.  Thanks for the patch Paul.

> Ignore Deprecations during build
> --------------------------------
>
>                 Key: HBASE-2364
>                 URL: https://issues.apache.org/jira/browse/HBASE-2364
>             Project: Hadoop HBase
>          Issue Type: Improvement
>    Affects Versions: 0.21.0
>            Reporter: Paul Smith
>            Assignee: Paul Smith
>            Priority: Trivial
>             Fix For: 0.21.0
>
>         Attachments: HBASE-2364-nodeprecations.patch
>
>
> I'd like to propose tweaking the Maven compiler plugin definition to ignore deprecations.
 firstly, during a Maven build, the deprecation output is totally ignored by everyone I'm
sure, and IDE's do a much better job of tracking these anyway, so the value to the output
is just not there.
> Secondly when one has this many deprecation warnings it's actually _hiding_ any compiler
errors.  I was in a conversation with 'adragomir' on IRC last night (my time) and he was bitten
by this, because the ERROR level stuff is done first, but quickly scrolls off the screen and
becomes hidden.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message