Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Shaded jar built with -Dgeotools keeps only one JAI-EXT registry file

Open
#3,443 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@jiayuasu is already working on this.

Since Oct 14, 2026.

  • #3444 by @jiayuasu — closed without merging
  • #3460 by @jiayuasu — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
25/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
java
Domain
build-system

Research direction

The fix lives in the shade plugin configuration of the sedona-spark-shaded module's pom.xml, which is the module built with the -Dgeotools profile. Check how the ServicesResourceTransformer or AppendingTransformer handles META-INF/registryFile.jaiext and META-INF/registryFile.jai, then confirm the shaded jar contains merged entries for both. Pull request 3460 is already open against this issue, so review or build on that work rather than starting a parallel fix.

Written by the indexing model from the issue text.

Description

When sedona-spark-shaded is built with -Dgeotools (as the Python CI does), the shade plugin keeps one META-INF/registryFile.jaiext instead of merging the files shipped by the ~30 JAI-EXT modules. Only Affine ends up registered as a JAI-EXT operation. Crop, Scale, Translate, Warp, Mosaic, BandMerge and others fall back to core JAI, and the JAI-EXT-only operations are missing. META-INF/registryFile.jai loses the JAITools ZonalStats entry the same way.

As a result, the Python tests run different raster code than releases (which get GeoTools from geotools-wrapper, where these files are merged) and than the Scala tests.

Fix: append both registry files in the shade configuration.

Dominant language
Java
Stars
2.4k
Forks
787
Avg merge
1d 23h
Merged PRs (30d)
52

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/sedona

All issues in apache/sedona

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.