[
https://issues.apache.org/jira/browse/THRIFT-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857341#comment-15857341
]
Christopher Tubbs commented on THRIFT-4074:
-------------------------------------------
My current workaround is to inject an unused method into every generated class
file after generation. (only classes, not enums, which do not have unused
items, except for what is described in THRIFT-4073).
{code}
find $BUILD_DIR/gen-java -name '*.java' -exec grep -Zl '^public class ' {} + |
xargs -0 sed -i.orig -e 's/^[}]$/ private static void unusedMethod() {}\
}/'
{code}
> Unnecessary suppress warnings (unused)
> --------------------------------------
>
> Key: THRIFT-4074
> URL: https://issues.apache.org/jira/browse/THRIFT-4074
> Project: Thrift
> Issue Type: Bug
> Components: Java - Compiler
> Affects Versions: 0.10.0
> Reporter: Christopher Tubbs
>
> Some generated Java files do not have unused variables. This results an a
> warning in some compilers (Eclipse, for one), that the warnings suppression
> for unused elements itself is unnecessary.
> Some unused variables appear to simply be unnecessary code generation. These
> should be removed.
> Others may affect serialization if changed, and are intentionally unused for
> backwards compatibility because they are class fields.
> If this is the case, the warnings suppression about them being unused should
> appear on the unused item itself when it is declared, rather than on the
> class as a whole.
> If these two steps are done, then there is no need to continue to suppress
> the unused types for all files, globally at the top of the file.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
