[
https://issues.apache.org/jira/browse/HADOOP-5663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699641#action_12699641
]
Jothi Padmanabhan commented on HADOOP-5663:
-------------------------------------------
While working on this, we stumbled on a javac bug where deprecated warnings do
not get suppressed when deprecated classes are used as method arguments. This
apparently is a known [bug|http://bugs.sun.com/view_bug.do?bug_id=6594914]. The
following code illustrates the problem -- warning in f1 is suppressed, but not
in f2
{code}
$ cat A.java
@SuppressWarnings("deprecation")
public class A {
public void f1 () {
B b = new B("abc");
b.fun();
}
public void f2(B b) {
b.fun();
}
}
$ cat B.java
@Deprecated
public class B {
private String s;
public B(String str) { s = str;}
public void fun() { System.out.println(s);}
}
{code}
{noformat}
$ javac -g -verbose -Xlint A.java B.java
.
.
A.java:8: warning: [deprecation] B in unnamed package has been
deprecated
public void f2(B b) {
^
{noformat}
> Resolve javac warnings in mapred
> --------------------------------
>
> Key: HADOOP-5663
> URL: https://issues.apache.org/jira/browse/HADOOP-5663
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Jothi Padmanabhan
> Assignee: Jothi Padmanabhan
>
> Towards a solution for HADOOP-5628, we need to resolve all javac warnings.
> This jira will try to resolve javac warnings where ever possible and suppress
> them where resolution is not possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
