Skip to content

build: update to Grobid 0.9.1 and align with software-mentions - #23

Merged
lfoppiano merged 4 commits into
devfrom
feature/grobid-0.9.1
Aug 5, 2026
Merged

build: update to Grobid 0.9.1 and align with software-mentions#23
lfoppiano merged 4 commits into
devfrom
feature/grobid-0.9.1

Conversation

@lfoppiano

Copy link
Copy Markdown
Collaborator
  • Bump grobid-core/service/trainer 0.9.0 -> 0.9.1
  • Dockerfile.datastet runtime base image 0.9.0-full -> 0.9.1-full
  • Align shared build.gradle scaffolding/comments with the sister software-mentions project (jackson-annotations rationale, git-xet note on the HF model clone, Gradle 9 exec{} comment) so the two build files diff cleanly down to domain-specific differences.

- Bump grobid-core/service/trainer 0.9.0 -> 0.9.1
- Dockerfile.datastet runtime base image 0.9.0-full -> 0.9.1-full
- Align shared build.gradle scaffolding/comments with the sister
  software-mentions project (jackson-annotations rationale, git-xet
  note on the HF model clone, Gradle 9 exec{} comment) so the two
  build files diff cleanly down to domain-specific differences.
Grobid is not published to Maven Central, so the 0.9.1 artifacts are
vendored into the project-local repo (as 0.9.0 was) to keep clean
checkouts and CI building without a prior grobid publishToMavenLocal.
Removed the superseded 0.9.0 jars. Verified resolution with mavenLocal
and the Gradle cache purged of 0.9.1.
No test uses PowerMock; remove powermock-module-junit4 /
powermock-api-easymock. Add an explicit junit:junit:4.13.2 because the
JUnit 4 API was previously provided transitively by
powermock-module-junit4 (JUnit 4 tests run via junit-vintage-engine).
Grobid 0.9.1 runs on Dropwizard 5.0.1 / Jetty 12, and grobid-service's POM
pulls that stack transitively, so the app must move too:
- build.gradle: dropwizard 4.0.17 -> 5.0.1, guicey 7.3.1 -> 8.0.2, add
  jetty-bom/jetty-ee10-bom 12.1.9 (CVE-2026-2332); slf4j-api 1.7.36 -> 2.0.17.
- Application: Jetty 12 removed org.eclipse.jetty.servlets CrossOriginFilter/
  QoSFilter; replace with the CrossOriginHandler/QoSHandler server handlers
  (as Grobid does) via environment.getApplicationContext().insertHandler(...).

Without this the service crashed on startup with
NoClassDefFoundError: org/eclipse/jetty/servlets/CrossOriginFilter.
Verified clean env: resolves dropwizard 5.0.1 + jetty 12.1.9 + opennlp 2.5.9;
onejar bundles CrossOriginHandler/QoSHandler.
@lfoppiano
lfoppiano merged commit 0ee27c0 into dev Aug 5, 2026
3 checks passed
@lfoppiano
lfoppiano deleted the feature/grobid-0.9.1 branch August 5, 2026 16:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant