[
https://issues.apache.org/jira/browse/HADOOP-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485309
]
Tom White commented on HADOOP-958:
----------------------------------
On 29/03/07, Doug Cutting <[EMAIL PROTECTED]> wrote:
> I think for this issue, which is not completely automatic, my hunch is
> to pursue it piecemeal. Also, as we more actively maintain multiple
> branches, the notions of just-before or just-after a release don't make
> quite as much sense, since these changes will affect merging. So doing
> it all at once in one release will make all merging harder for that
> release, while spreading it over multiple releases will spread the merge
> pain out. That said, if someone has a patch ready that updates the
> whole tree and that applies cleanly to trunk at a time when the patch
> queue is empty, then I'd vote to just commit it and deal with the
> consequences. However the patch queue hasn't been empty for a while...
My patch of three days ago has already been invalidated by other patches. So in
practice I think this has to be done piecemeal. If the pieces can be applied in
quick succession then great, but that may not be easy either. I agree about
keeping them to one release though, and hope that would be possible.
I will try to get back to this when the patch queue clears...
> Building Hadoop results in a lot of warnings
> --------------------------------------------
>
> Key: HADOOP-958
> URL: https://issues.apache.org/jira/browse/HADOOP-958
> Project: Hadoop
> Issue Type: Improvement
> Reporter: eric baldeschwieler
> Attachments: example-warnings.patch, fs-unchecked.patch
>
>
> We are getting hundreds of warnings right now. Most of these are a result of
> our transition to 1.5 and deprecated uses of generics. We should still fix
> these, since producing lots of warnings:
> A) Leads to the perception that our code is of low quality
> B) Can mask warnings that come from real issues.
> ---
> I suggest we do two things
> 1) Submit a patch or set of patches to clean this up
> 2) Change our patch tester to validate that the number of warnings per build
> did not go up with this patch
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
