Community
Participate
Working Groups
If a role file contains non-externalized string constants and if these should be reported as warnings or errors, the following issues are observed: - the $NON-NLS-<n>$ doesn't silence a warning - compiler and reconciler behave differently
Created attachment 175584 [details] test and fix Tests are OTReconcilerTests.testNLSinRoFi1 f. and testA113_suppressWarnings1 f. The issue was caused by multiply processing the same CUD, which caused trouble because the nlsTags are consumed during analysis, thus subsequent analysis would no longer find the tags to silence the warning: - TypeDeclaration.resolve caused duplication (class/ifc part) - the reconciler additionally calls CompilationUnitDeclaration.resolve (compiler normally descends via team unit -> team type -> role type) Fixed by additional guards before calling unit.reportNLSProblems()
Patch has been committed as r648 f.
Verified using I201009211735