uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (JIRA)" <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-6054) JCasGen generating warnings by creating deprecated constructors
Date Fri, 07 Jun 2019 14:09:00 GMT

    [ https://issues.apache.org/jira/browse/UIMA-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858682#comment-16858682
] 

Marshall Schor commented on UIMA-6054:
--------------------------------------

hmmm, I don't think this will work in many cases (that I can think of...).  Here's one: 
A user has converted to uima version 3 and is running with some type system hierarchy. 

They then regenerate one of their types, TTT, whose supertype is TTTSSS, whose supertype is
Annotation.

The hasDeprecatedDefaultConstructor(TTTSSS)  would return false, but in fact, because it
was generated before this change went in, it would need to return true.  Did I miss something?

> 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
>
>
> 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)

Mime
View raw message