-
Notifications
You must be signed in to change notification settings - Fork 440
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
Preparation release 0.8.1 #1123
base: master
Are you sure you want to change the base?
Conversation
I've ran the evaluation with a partial glutton (around 80-90M records from Since I don't have a GPU machine I can log in, I
Since I did not use the standard method, this should be taken with a pinch of salt. TLDR: Header metadata and citation context performances have decreased, the rest as increased.
|
I'm attaching all the results as files for completeness: |
Hi Luca ! I think there is a major issue with the the jvm version indicated by the Kotlin jvmToolchain
The classes and jar become incompatible with jvm lower than 17... So it's not possible to run grobid any more with a jvm 11:
In addition, it has blocking consequences for other modules and libraries using grobid which can't be run with jvm 17. The solution seems to simply make everything to java 11:
although source compatibility java 11 is not working:
gives
|
It seems the Java 11 compatibility is broken by the recent changes in FundingAcknowledgementParser:
|
Hi @kermitt2, I checked grobid-quantities, software-mentions, datastet and they seems to be compatible with JDK 17. I would say that the old modules may stay with an older version. If you want to keep jdk 11 compatibility, for the second problem, you can replace |
I think it's good to move to JDK 17 in general, but we need to update the other modules first, otherwise this is blocking for users. This is also a general issue for everything that depends on Grobid and for existing production environment where Grobid runs. For example I am currently stuck and failed to upgrade entity-fishing from JDK 8 to JDK 11 and this is very annoying for the users. I think it's better to ensure JDK 11 compatibility for this release - 17 would be a breaking change for version 0.9.0, especially given that the move to 17 is more for our comfort than providing really actual advantages? |
OK, no problem. I might be to optimistic in thinking that people would have migrated to Docker by now. Let me help you with entity-fishing. Could you commit and push everything you've done so far on a branch of the project, I will have a look ASAP 😉
Sure. 👍 |
Thank you very much @lfoppiano it is working also for me now with jdk 11 on Linux (as you, I usually run jdk 17, and it's why I saw the issue only recently). About entity-fishing, the master has the latest commit if I am not wrong, and running with grobid 0.8.0 and jdk 11 fails because the current version uses an incubator module that has disappeared after jdk 1.8. I did not analyze further which dependency uses this module and if there is a possible replacement in jdk 11. |
This PR contains the updates for the release 0.8.1