Hi,

here’s my own +1 (binding).

Env:

Apache Maven 3.9.14 (996c630dbc656c76214ce58821dcc58be960875b)
Maven home: /Applications/apache-maven-3
Java version: 25.0.2, vendor: Eclipse Adoptium, runtime: 
/Library/Java/JavaVirtualMachines/temurin-25.0.2.jdk/Contents/Home
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "26.3.1", arch: "aarch64", family: „mac"

Thx @rzo1 for the findings & notes: 

ad (1): opennlp-uima-descriptors where present at the same location in all 
previous releases I know of.
ad (2): nice finding, needs investigation / Jira - no blocker though
ad (3): nice finding, needs investigation / Jira - no blocker though


Best
Martin | mawiesne

> Am 25.03.2026 um 08:57 schrieb Richard Zowalla <[email protected]>:
> 
> Hi all,
> 
> thanks for putting it together. Run my checks on the following dev system:
> 
> Apache Maven 3.9.14 (996c630dbc656c76214ce58821dcc58be960875b)
> Maven home: /home/tmpl/.sdkman/candidates/maven/current
> Java version: 21.0.6, vendor: Eclipse Adoptium, runtime: 
> /home/tmpl/.sdkman/candidates/java/21.0.6-tem
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "linux", version: "6.17.0-14-generic", arch: "amd64", family: "unix"
> 
> ---
> 1. Build from source with tests
> 2. Checked the signatures and hashes using 
> https://gist.github.com/rzo1/9573dd66f401eb0b2af72153bd49bb2a
> 3. Consumed the staging maven artifacts (model resolver, lang detect, 
> sentence) in one of my projects - worked fine.
> ---
> 
> Notes:
> 
> - The "opennlp-uima-descriptors" in /docs seem a bit off. Don't know if they 
> should be in that directory.
> - Generated PDF is a weird split in its title "Apache OpenNLP De-
> veloper Documentation" - we might want to fix that in the next iteration.
> - If the OPENNLP_HOME in the Shell Script contains a special char like 
> "apache-opennlp-3.0:(2).0-M2-bin" as folder name, this will break current 
> shell code regarding classpath resolution. We might want to make that more 
> robust against weird user installation directories.
> 
> I vote: +1 (binding)
> 
> Gruß
> Richard
> 
> On 2026/03/24 07:09:34 Martin Wiesner wrote:
>> Hi all,
>> 
>> I have posted a first release candidate for the Apache OpenNLP 3.0.0-M2 
>> release and it is ready for testing.
>> 
>> The 3.x release line of Apache OpenNLP introduces no known breaking changes 
>> while significantly modularizing the project to improve library usage and 
>> future extensibility.
>> The core API remains stable and fully compatible with 2.x, so existing 
>> projects can continue using the opennlp-tools artifact without (substantial) 
>> modifications.
>> 
>> Key Highlights:
>>   • Notable Changes: 
>>       • The minimum Java compiler level was raised to 21 (OPENNLP-1735)
>>       • The artifact 'opennlp-models' was renamed to 
>> 'opennlp-model-resolver'. It can be used to detect and load OpenNLP 
>> compliant models from the classpath (OPENNLP-1807)
>>   • New Features: 
>>       • Apache OpenNLP can now detect sentiment from text (OPENNLP-855)
>>       • The eval corpus format for GermEval2014 is now supported 
>> (OPENNLP-976)
>>       • Document Categorization is now possible via a binding to LibSVM 
>> (OPENNLP-1808)
>>   • Bug Fixes:
>>       • The SentenceDetector got three fixes in handling edge cases with 
>> abbreviation dictionaries (OPENNLP-1809, OPENNLP-1810, OPENNLP-1811) - NOTE: 
>> These fixes will be back-ported to the upcoming OpenNLP release 2.5.8 as 
>> well.
>>   • Improvements:
>>       • Language Codes passed in are now stricter validated to comply with 
>> ISO-693 standard (OPENNLP-991)
>>       • The OpenNLP developer manual (HTML + PDF) got an uplift for the UIMA 
>> documentation part, being largely extended (OPENNLP-49)
>> 
>> Thank you to everyone who contributed to this release, including all of our 
>> users and the people who submitted bug reports, contributed code or 
>> documentation enhancements.
>> 
>> The release was made using the OpenNLP release process, documented on the 
>> website:
>> https://opennlp.apache.org/release.html
>> 
>> Maven Repo:
>> https://repository.apache.org/content/repositories/orgapacheopennlp-1061
>> 
>> <repositories>
>> <repository>
>> <id>opennlp-3.0.0-M2-RC1</id>
>> <name>Testing OpenNLP 3.0.0-M2 release candidate</name>
>> <url>
>> https://repository.apache.org/content/repositories/orgapacheopennlp-1061
>> </url>
>> </repository>
>> </repositories>
>> 
>> Binaries & Source:
>> 
>> https://dist.apache.org/repos/dist/dev/opennlp/opennlp-3.0.0-M2-rc1/
>> 
>> Tag:
>> 
>> https://github.com/apache/opennlp/releases/tag/opennlp-3.0.0-M2
>> 
>> Tag Hash: 4cc735b50edca7618cef067574ae5804089170db
>> 
>> Release notes:
>> 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12356724&projectId=12311215
>> 
>> The results of the eval tests for the aforementioned tag can be found
>> here: https://ci-builds.apache.org/job/OpenNLP/job/eval-tests-releases/25/
>> 
>> Reminder: The up-2-date KEYS file for signature verification can be
>> found here: https://dist.apache.org/repos/dist/release/opennlp/KEYS
>> 
>> Checklist for reference:
>> 
>> [ ] Both source (tar.gz/zip) and binary artifacts (tar.gz/zip) are present, 
>> along with .asc and .sha512 files for each.
>> [ ] PGP signatures are valid for the release artifacts using the KEYS file 
>> from dist.apache.org
>> [ ] SHA512 checksums are correct and verified.
>> [ ] LICENSE and NOTICE files exist and are accurate.
>> [ ] No unexpected binary files in the source release.
>> [ ] All source files have appropriate ASF headers (excluding generated files 
>> and legacy files).
>> [ ] Build completes successfully from source and the instruction to do so 
>> are clear.
>> 
>> Please vote on releasing these packages as Apache OpenNLP 3.0.0-M2
>> The vote is open for at least the next 72 hours.
>> 
>> Only votes from OpenNLP PMC are binding, but everyone is welcome to
>> check the release candidate and vote.
>> The vote passes if at least three binding +1 votes are cast.
>> 
>> Please VOTE
>> 
>> [+1] go ship it
>> [+0] meh, don't care
>> [-1] stop, there is a ${showstopper}
>> 
>> Thanks!
>> Martin | mawiesne

Reply via email to