-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade morfologik from 1.10.0 to 2.0.1 #342
Conversation
Thanks! I wonder why you also added |
I had to add commons-cli because standalone + tools use it but morfologik no longer does, so it's not pulled in transitively. See below for the relevant output from Would you like me to move the version into parent properties? It looks like you have this for some dependencies but not all, so I wasn't sure which you'd prefer. Also do you have documentation on dictionary generation? It looks like the explicit SUFFIX error will make this upgrade more painful than I originally thought. I'm not sure how to proceed with re-generating dictionaries. before morfo upgrade
after morfo upgrade
|
|
Jaume has made the update, so I will close this request. Please let us know if you think there are still problems. |
Thanks @danielnaber, upgrading from 3.1 to 3.3 fixes the version conflict I had for However, the upgrade also produces the following dependency convergence error with maven-enforcer-plugin:
I think this issue was introduced with morfologik/morfologik-stemming@3ada8d8 - the Any thoughts on this? I can reach out to dweiss if you think that makes sense |
Yes, sounds like a problem on the morfologik side if I get it correctly. Would be nice if you could contact them. |
Sounds good, I will keep you posted on the status there - if a 2.1.1 patch gets pushed out, it would be great to see a new languagetool release that uses it. Also, it would be nice if languagetool enforced dependency convergence, so that any user enforcing it in their project could count on convergence within the single languagetool dependency. It should speed up development time too if you ever have clashing dependency versions - instead of finding out at runtime that the wrong version of a library is on the classpath, you'll get an error in the |
Sounds good, a pull request to the pom.xml is welcome. |
This also upgrades carrotsearch hppc, which will make languagetool 3.2 compatible with other projects that depend on the newest version of hppc.
TODO
Use an explicit fsa.dict.encoder=SUFFIX metadata key
Deprecated encoder keys in metadata. Use fsa.dict.encoder=SUFFIX