[
https://issues.apache.org/jira/browse/UIMA-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16860009#comment-16860009
]
Marshall Schor commented on UIMA-6054:
--------------------------------------
ok, it looks like the main idea is to mark the 0-arg constructor as deprecated,
except when the superclass's constructor is not deprecated.
I think it may be better to mark *all* generated 0-arg constructors as
deprecated, because they should not be used, and it would be good to note that
with the deprecation annotation. Users should never have made use of these,
so it's not really a question of suggesting to users to "migrate away" from
these. It's more a way to remind users if they accidentally code this, that
they should rethink what they're doing.
I don't think there's any negative consequence or Eclipse warnings, etc. from
this, but please let me know if this is not right.
> JCasGen generating warnings by creating deprecated constructors
> ---------------------------------------------------------------
>
> Key: UIMA-6054
> URL: https://issues.apache.org/jira/browse/UIMA-6054
> Project: UIMA
> Issue Type: Bug
> Components: UIMA
> Affects Versions: 3.0.2SDK
> Reporter: Hai-Son Nguyen
> Priority: Trivial
> Attachments: patch-uima-6054v1.txt, patch-uima-6054v2.txt,
> patch-uima-6054v3.txt, patch-uima-6054v4.txt
>
>
> The JCasGen process produces classes with a protected empty no parameter
> constructor.
> Base classes that have extended the Annotation class
> (org.apache.uima.jcas.tcas.Annotation) are now getting warnings that the
> constructor Annotation() is deprecated.
> The constructor documentation states, "Never called. Disable default
> constructor" but the presence of other constructors already serve this
> purpose.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
