[
https://issues.apache.org/jira/browse/UIMA-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977401#action_12977401
]
Marshall Schor commented on UIMA-1983:
--------------------------------------
Are there two name shadowing instances: ..._Type.featOkTst and
..._Type.typeIndexID ?
If the problem is just the warning messages, we can fix that by changing the
generator to generate
@SuppressWarnings("hidden") to those two fields.
Are there other fields giving problems, or just those two?
> JCasGen prouces source files with name shadowing/conflicts
> ----------------------------------------------------------
>
> Key: UIMA-1983
> URL: https://issues.apache.org/jira/browse/UIMA-1983
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Reporter: Philip Ogren
> Priority: Minor
>
> When the compiler warnings are set to complain when name shadowing or name
> conflicts exist, then the source files produced by JCasGen contain many
> warnings. It sure would be nice if these files came out pristine rather than
> having compiler warnings. Eclipse does not seem to allow for fine grained
> compiler warning configuration (i.e. to ignore certain warnings for certain
> source folders or packages) but only works at the project level.
> Therefore, I must either turn these warnings off for the entire project or
> must ignore the warnings in the type system java files.
> I'm guessing that this is a side effect of an intentional design decision (re
> eg typeIndexID) and so I am not that hopeful that this can be fixed but
> thought I would ask anyways.
> Thanks,
> Philip
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
