Skip to content

Conversation

@headius
Copy link
Member

@headius headius commented Jan 22, 2026

This cleans up the existing Chicory experiment and moves closer to a separate SPI for the Chicory-based Prism parser.

  • Using artifact org.jruby:chicory-prism:0.0.1-SNAPSHOT
  • Build cleaned up to avoid release plugins during local builds and bump to 2.0.0-SNAPSHOT
  • Use release version of JRuby 10
  • Begin separating the native and wasm prism backends into separate services.

If gpg fails you can't install locally, and the rest are not
interesting for local builds.
Both forms are still in the same provider, but separated into two
classes. The ParserProvider logic for JRuby may need some tweaks
to support two separate SPIs so this is a first step to isolating
them.

The native parser will be returned if:

* A dynamic library file provided to initialize exists, and
* the wasm parser has not been specifically requested.

The wasm parser will be returned if:

* It was specifically requested, or
* a dynamic library that exists has not been provided to
  initialize.

In the future this selection should happen closer to the JRuby
level so we can use either or both more easily.
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