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 Thu, 06 Jun 2019 13:58:00 GMT

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

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

I'm thinking this may cause backwards compatibility issues, for this use case:

The default empty constructor is removed for Type XXX.  But there exists somewhere else,
in a separate compilation unit or project, a type XXX_S whose parent is XXX.  Then when XXX_S
is loaded to run or compile, you get an error.

Perhaps a better fix would be to add an annotation @SupressWarnings("deprecation") to these?

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