Problem
The cuvs-lucene service descriptor republishes Lucene-owned vector-format providers already registered by Lucene itself, and current tests do not assert the exact contents or fresh-JVM behavior of the published thin JAR.
Proposed change
- Register only providers owned and shipped by cuvs-lucene.
- Add a post-package integration test against the actual thin JAR.
- Verify exact SPI descriptors and owned production classes.
- Exclude Lucene classes, base cuvs-java classes, dependency payloads, and test-only diagnostics.
- Resolve packaged providers in a fresh JVM without
target/classes masking omissions.
The logical provider set remains unchanged when the declared Lucene dependency is present. Related to #2512.
Problem
The cuvs-lucene service descriptor republishes Lucene-owned vector-format providers already registered by Lucene itself, and current tests do not assert the exact contents or fresh-JVM behavior of the published thin JAR.
Proposed change
target/classesmasking omissions.The logical provider set remains unchanged when the declared Lucene dependency is present. Related to #2512.