[ 
https://issues.apache.org/jira/browse/UIMA-4158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Eckart de Castilho updated UIMA-4158:
---------------------------------------------
    Description: 
We have constants defined in CasImpl, but they are not public 
THROW_EXCEPTION_FS_UPDATES_CORRUPTS. I would like to set such properties 
programmatically from unit tests and having these constants public would be 
very convenient for this. E.g. I would immediately notice when such 
functionality is changed/removed, e.g. as has happened in recent changes 
related to UIMA-4135. 

Mind that CASImpl.CHK_FS_UPDATES_CORRUPTS had been public while it still had 
existed.

  was:We have constants defined in CasImpl, but they are not public 
THROW_EXCEPTION_FS_UPDATES_CORRUPTS. I would like to set such properties 
programmatically from unit tests and having these constants public would be 
very convenient for this. E.g. I would immediately notice when such 
functionality is changed/removed, e.g. as has happened in recent changes 
related to UIMA-4135. 


> Make THROW_EXCEPTION_FS_UPDATES_CORRUPTS and friends public
> -----------------------------------------------------------
>
>                 Key: UIMA-4158
>                 URL: https://issues.apache.org/jira/browse/UIMA-4158
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>    Affects Versions: 2.7.0SDK
>            Reporter: Richard Eckart de Castilho
>            Priority: Minor
>             Fix For: 2.7.1SDK
>
>
> We have constants defined in CasImpl, but they are not public 
> THROW_EXCEPTION_FS_UPDATES_CORRUPTS. I would like to set such properties 
> programmatically from unit tests and having these constants public would be 
> very convenient for this. E.g. I would immediately notice when such 
> functionality is changed/removed, e.g. as has happened in recent changes 
> related to UIMA-4135. 
> Mind that CASImpl.CHK_FS_UPDATES_CORRUPTS had been public while it still had 
> existed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to