Github user bgould commented on the issue:
https://github.com/apache/thrift/pull/1120
@jeking3
Yes exactly. I added it to the build process that compiles the java unit
tests... so if some change to compiler introduces a regression, the IDL in that
file should fail to compile. I didn't add a unit test for this as I felt that
the compilation itself was the test.
Consider the following IDL:
struct String {
1: string val
}
struct Object {
1: map<string, String> somemap
}
It would be possible to make a modification to the compiler that
erroneously generates the map type as `java.util.Map<String, String>` instead
of `java.util.Map<java.lang.String, String>` or to add some reference in the
generated code to `java.lang.Object` that is not fully-qualified... however
with the generated classes above in the `thrift.test` package, `javac` should
flag the unqualified reference(s) as ambiguous.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
