# Swift/Java Interop Community Call #1

**URL:** <https://forums.swift.org/t/swift-java-interop-community-call-1/82921>\
**Category:** Java interoperability\
**Created:** [October 29, 2025, 6:42am UTC](https://forums.swift.org/t/swift-java-interop-community-call-1/82921 "2025-10-29T06:42:42Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![ktoso](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/ktoso/32/44526_2.png) [@ktoso](https://forums.swift.org/u/ktoso)\
**Post date:** [November 6, 2025, 3:05pm UTC](https://forums.swift.org/t/swift-java-interop-community-call-1/82921/4 "2025-11-06T15:05:39Z")

</div>

Meeting notes from the first Swift/Java interoperability call.

# Swift Java Community Call Notes

- Konrad
- Mads
- Thomas
- Greg
- Joannis
- Marc
- Finagolfin\*

## Agenda:

- Swift Java “JNI only” Package status -- Marc

- Android & JNIOnLoad fun? -- Mads

- How can we contribute, is there some guide about patterns to follow? -- Greg

- (Old) Android example issues -- Thomas

- Packaging and how to link – Mads

- **ACTION** : Greg, some quick update to the android example how to add dependencies

Status updates:

- Mads:
  - jextract+jni: async funcs are now imported as `CompletableFutures` (API 24)
  - jextract+jni: working on nested types in Swift
  - jextract+jni: implementing Java "interfaces" as protocols using Swift type

- Konrad:
  - Working on calling Java funcs from Swift and automatic import of Java APIs (wrap-java)

- Please try things out and report issues for things that don’t work

Gradle plugins / building:

- Konrad: Discussion about building -linux-arm64-6.2.1.jar etc, vs REALLY fat jars etc
  - Really use-case dependent, some people want one or the other; a Gradle plugin could simplify this a bit, because it’s really tricky to get right at first.

- Marc: Skip builds
  - AAR, every swift build takes the .so files and bindings and THEN the AARs are put together into an APK

- ABI compatibility discussion
  - Lack of ABI kinda troublesome adoption because matching Swift versions would lead to “everyone rebuild for new Swift version”, however short term this may be managable;
  - This is kind of new with the arrival of swift-java and jars which contain binary compiled Swift; Server projects didn’t really encounter this up until now.

## Next call

We will schedule another call in 2 weeks time, I will share a meeting link and exact date in a new forums thread.

---

_[View the full topic](https://forums.swift.org/t/swift-java-interop-community-call-1/82921)._