-
Notifications
You must be signed in to change notification settings - Fork 100
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
Update Stanford NLP #643
base: master
Are you sure you want to change the base?
Update Stanford NLP #643
Conversation
Otherwise get "[error] [launcher] error during sbt launcher: java.lang.UnsupportedOperationException: The Security Manager is deprecated and will be removed in a future release" on Java 18.
It seems to be incredibly slow
This might be superseded by PR #644 now, no? |
Check StanfordCoreNLP version
#644 was merged into this one. Weren't you saying that the version number needs a significant bump here, like to 9, and that some projects, maybe reach and possibly eidos, would need to stay at 8? This one might be 9.5.2 and the old might be 8.5.2 and for some time there might be a need to update them in parallel. If there is some change in 9.6 that should be available to old programs, it would be added to 8.6. That would probably necessitate having a processors8 branch that parallels master. If someone is fiddling with branches, maybe it's time to swap out master for main as well. Before this is merged, I should test once more on Java 18 locally. I'd also like to check over the old issues related to the problems with the instability of the stanford output. |
This strategy of keeping parallel minor versions is new to me. I was thinking of simply bumping this to 9.0.0. You prefer your idea because it allows us to develop in parallel? |
The merge is currently waiting for me to figure out this error observed when the change is integrated into Eidos. It's unlikely to be the only problem.
|
The version number is not critical for me. There can be a more complicated mapping. Maybe it's more important to have a logical progression of numbers in the main branch and not skip numbers based on (perceived) needs of a side branch. |
|
The problem above was solved with
After that, the tests run. For my records, these below are then failing. I suspect that it comes from changing of tags, like: TO -> IN I don't know whether it's worth updating any rules or hard-coded tags. Eidos doesn't necessarily need to use this processors update.
|
Probably true. But do you have more concrete examples where some of these fail? |
No description provided.