Hi, we’ll make some changes to the LanguageTool release process with LT 6.6, planned for 2025-03-27.
Daniel hands over the LT maintenance to the company that runs LanguageTool. Stefan Viol will take care of it.
We’ll stop making releases as ZIP files. Instead, users can just download the latest snapshot from https://internal1.languagetool.org/snapshots/. Creating the ZIP releases takes quite some time and adds no value for users compared to using a snapshot.
We’ll make a final 6.6 release that documents the new release process and points users to the snapshots for any upcoming changes.
We plan to make another release of the Java JARs at Maven Central with the code of LT 6.6. We still need to decide whether we’ll keep making releases at Maven Central in the future. Feel free to post your feedback here, e.g. wheter you have a use case that relies on the LT artifacts being published at Maven Central.
Everything will still be available in git, so everyone can build it themselves. I don’t think the Wikipedia check tool has a significant number of users, so I don’t think it’s worth to provide a release.
I do have a set of tools for text processing for Ukrainian that use LT artifacts from Maven Central (technically only languagetool-core and language-uk).
If we stop generating them I’ll need to find another way to consume them.
I’m not sure if I understood the points correctly. Is it true that there will continue to be releases of LanguageTool (e.g. 6.7)?
If so, will these releases continue to be available at JFrog?
WritingTool depends on these releases (and the snapshots as well).
Some time ago, we made a clearer separation between the open-source part and the close-source part.
For the automatic tests and also for our developers, however, we needed a Maven repo to be able to provide the OS artifacts (without the need to build them locally on every change).
See “test-after-os-commit” and “test-and-deploy-partial”
So currently, with every commit in the master branch OS, a new snapshot of the modules is uploaded to the JFrog repo (in the best case, only what has been changed).
We use the same JFrog repo for our weekly premium releases (that’s where the versioned files in the repo come from).
Currently, however, only the snapshots are still uploaded. The weekly premium releases are now moved to another tool. Because of this, there are almost no versioned OS files anymore in our JFrog repo.
The few exceptions that have been added here in the past 6 months were tests or other.
I’m sorry, but I still don’t fully understand.
I use the Maven artifacts of the LT snapshots for the WritingTool snapshots.
For my releases, I have so far used the last stable LT release (also as a Maven artifact).
If I understand correctly, nothing will change in the snapshots.
My question is now: What about the releases (6.6, 6.7, …)? Will they continue to exist as Maven artifacts?
