mrunit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bertrand Dechoux (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MRUNIT-117) Fix compiler warnings
Date Mon, 12 Nov 2012 08:22:13 GMT

    [ https://issues.apache.org/jira/browse/MRUNIT-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495147#comment-13495147
] 

Bertrand Dechoux commented on MRUNIT-117:
-----------------------------------------

We could create a top task for next version(s) and list the remaining issues.
* There might be a way to customize the maven build in order to fail on warnings.
* We might want to probe sonarsource about http://nemo.sonarsource.org/.
* In Hadoop (I think), and other apache projects, there is scoring bot for commits. I don't
know how it works but it could be investigated too.
* ...
                
> Fix compiler warnings
> ---------------------
>
>                 Key: MRUNIT-117
>                 URL: https://issues.apache.org/jira/browse/MRUNIT-117
>             Project: MRUnit
>          Issue Type: Improvement
>    Affects Versions: 1.0.0
>            Reporter: Dave Beech
>            Assignee: Dave Beech
>            Priority: Minor
>
> I see this has been raised before (MRUNIT-18) but it looks like the number of compiler
warnings has built up again. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message