[CI][Java] *-sources.jar include *.{so,dylib,dll}
- Dominant language
- Java
- Stars
- 94
- Forks
- 152
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 11
Description
### Describe the bug, including details regarding any error messages, version, and platform.
https://github.com/ursacomputing/crossbow/releases/tag/nightly-packaging-2024-02-08-0-github-java-jars
For example, `arrow-dataset-16.0.0-SNAPSHOT-sources.jar` includes the following:
```console
$ find arrow-dataset-16.0.0-SNAPSHOT-sources | grep -E '\.(so|dylib|dll)'
arrow-dataset-16.0.0-SNAPSHOT-sources/arrow_dataset_jni/aarch_64/libarrow_dataset_jni.dylib
arrow-dataset-16.0.0-SNAPSHOT-sources/arrow_dataset_jni/aarch_64/libarrow_dataset_jni.so
arrow-dataset-16.0.0-SNAPSHOT-sources/arrow_dataset_jni/x86_64/libarrow_dataset_jni.dylib
arrow-dataset-16.0.0-SNAPSHOT-sources/arrow_dataset_jni/x86_64/arrow_dataset_jni.dll
arrow-dataset-16.0.0-SNAPSHOT-sources/arrow_dataset_jni/x86_64/libarrow_dataset_jni.so
```
Those binaries are too large. So we should avoid this.
### Component(s)
Continuous Integration, Java
Contributor guide
Research direction
Start by inspecting the nightly Java release artifact linked in the issue and reproduce the `find` check against its `*-sources.jar` contents. Trace the CI or packaging step that assembles these source archives; done means the source jars no longer contain `.so`, `.dylib`, or `.dll` files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100