Hi,

   1. source build
   
................................................................................
   OK
      1. JavaDoc Warnings
   2. checked issues fixed list
   .............................................................. OK
   3. spotchecked license, notice, release-notes
   ................................. OK
   4. checked update site & tested with Eclipse 2022-06
   ..................... OK


[x] +1 OK to release

Viorel

On Wed, Oct 19, 2022 at 4:06 PM Richard Eckart de Castilho <r...@apache.org>
wrote:

> Hi,
>
> the Apache UIMA Java SDK 3.3.1 RC 1 has been staged.
>
> This is a bugfix release.
>
> **Bugs fixed**
> * 🦟 Issue #255: File handle leak accessing performanceTuning.properties
> * 🦟 Issue #240: Helper annotation created by SelectFS should not survive
> * 🦟 Issue #238: Form 6 serializes non-reachable FSes but should not
> * 🦟 Issue #235: Misleading error message when JCas type is not registered
> * 🦟 [UIMA-6479] PearPackagingMavenPlugin has ancient JUnit dependency
> * 🦟 [UIMA-6473] CasToComparableText is broken
>
> **Improvements**
> * ⭐️ Issue #222: Support comparing test files irrespective of line endings
> * ⭐️ [UIMA-6480] Add tests with empty arrays to CAS de/ser-suite
>
> **Refactoring**
> * ⚙️ [UIMA-6454] Update dependencies
> * ⚙️ [UIMA-6463] Use toolchains to ensure compatibility with Java 1.8
> * ⚙️ [UIMA-6469] Cleaning up file handling code
>
> Issues:
> https://github.com/apache/uima-uimaj/issues?q=milestone%3A3.3.1
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%203.3.1SDK
> Dist. artifacts:
> https://dist.apache.org/repos/dist/dev/uima/uimaj-3.3.1-rc-1/
> Eclipse Update Site:
> https://dist.apache.org/repos/dist/dev/uima/uimaj-3.3.1-rc-1/eclipse-update-site-v3/uimaj/
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapacheuima-1289/
> GitHub tag:          https://github.com/apache/uima-uimaj/tree/uimaj-3.3.1
>
> Please vote on release:
>
> [ ] +1 OK to release
> [ ] 0   Don't care
> [ ] -1 Not OK to release, because ...
>
> Thanks.
>
> -- Richard
>
>

Reply via email to