Contents

bastie/javapi4swift

This project provides a Java like API in 100%-pure Swift instead bridging to Java virtual machine. In result you do not need a Java virtual machine. On the otherside you can port Java code to Swift without Big-Bang step by step.

AI-assisted development

Starting 2026 June 1, this project uses AI (artificial intelligence) in addition to HI (human intelligence) to support the porting work. AI assistance is applied on top of the existing implementation base.

License

This project use only business friendly permissive licenses.

<p><figure> <a title="David A. Wheeler, et al., CC BY-SA 3.0 &lt;https://creativecommons.org/licenses/by-sa/3.0&gt;, via Wikimedia Commons" href="https://commons.wikimedia.org/wiki/File:Floss-license-slide-image.svg"><img width="1024" alt="Floss-license-slide-image" src="https://github.com/bastie/JavApi4Swift/blob/main/Sources/JavApi/JavApi⁴Swift.docc/Resources/Floss-license-slide-image.svg"></a> <figcaption style="text-align: right;display: inline-block">Image: David A. Wheeler, et al., CC BY-SA 3.0 <https://creativecommons.org/licenses/by-sa/3.0>, via Wikimedia Commons</figcaption> </figure></p>

Parts of source code use the BSD Licenses and the Public Domain / The Unlicense. By default I use the MIT License. Parts of source code use the Apache 2.0 license.

Similar projects

  1. JavApi⁴Swift

pro: it is JavApi⁴Swift 😎 pro: still active pro: no Java Runtime needed pro: stable pro: sample ported Java projects are provided contra: less developer contra: at the moment not all of Java API supported contra: Java code need to port to Swift

  1. Swift Java Interoperability Tools and Libraries

pro: subrepository of Apple Swiftlang github home pro: seems active pro: lot of developer pro: all of installed Java Runtime is supported pro: no rewrite of running Java code needed (it 's like let COBOL code run forever 😜) contra: need installed Java Runtime * contra: not stable

  1. java_swift - forks and similar projects of SwiftJava user.

pro: all of installed Java Runtime is supported contra: seams still inactive * contra: need installed Java Runtime

Some other projects port parts of Java functionally to Swift. I do not say one project are better than other.

thanks

Special thanks to contributors of

Usage

When working with XCode add dependency

https://github.com/bastie/JavApi4Swift.git

When working with SwiftPM add dependency

.package(url: "https://github.com/bastie/JavApi4Swift.git", from: "0.48.0")

or

.Package(url: "https://github.com/bastie/JavApi4Swift.git", .upToNextMajor(from: "0.48.0"))

Ports

I'm implementing some porting projects to check JavApi⁴Swift releases and look for the next missing features. The use should start from version 0.31.0. Check out these projects and learn how to use JavApi⁴Swift.

0.4.2

  • ASCII-Data is a library to display tables and graphs on command line as ASCII or ANSI.

0.7.4

  • LStXML2Code is a library and CLI to generate source code for German income tax calculation based on Federal Ministry of Finance provided XML Pseudocode.

0.8.0

  • iban4j is a library for generation and validation of the International Bank Account Numbers (IBAN ISO_13616) and Business Identifier Codes (BIC ISO_9362).

0.12.0

  • ShrinkItArchive is a library for managing Apple ][ ShrinkIt / NuFX archives.

0.19.1

  • STar is a simple Swift Tar library, that provides an easy way to create and read tar files using.

0.26.1

  • Word2Number is a converter library, to get numeric values from textual words f.e. 201 from two hundred and one. It is ported from non-i18n python project to i18n python project, to Java (and other) and now to Swift.

0.35.0

  • stailf is a tail -f implementation using the RandomAccessFile.

Development

include other projects

To honor the work of the developer of other project let the history come inside.

To include other project with compatible license do

# Example for some types from a jzlib clone # # clone the other project local, jzlib clone are here https://github.com/kohsuke/jzlib.git

git clone https://github.com/kohsuke/jzlib.git otherProject

# go into project directory and remove the origin cd otherProject git remote rm origin

# filter project to remove all unwanted data and commit it git filter-branch --subdirectory-filter src/main/java/com/jcraft/jzlib -- --all git rm Deflat.java GZIP.java Inf.java Z.java Tree.java StaticTree.java JZl*.java git commit -m "ready to import"

# go to JavApi project directory cd ../JavApi4Swift

# add (temporary) the local other project as remote source and pull wanted data with history git remote add importSource ../otherProject git pull importSource master --no-rebase --allow-unrelated-histories git remote rm importSource

# work on conflicts f.e. in .gitignore

# optional take a look into history git log

JavApi style guide

  1. The ported Java source code should not to modify more than needed.
  2. I like short lines and so indent is 2 spaces.
  3. Types are in same name files like Java with the exception of java.lang types.
  4. The opend curly braces are in the same line.
  5. packages are mapped over enums in files named as java.basepackagename.packagename.swift in result of compiler problems with more than one identical files names.
  6. Exported parameters of Java translated, non-private function parameter are marked with underline.
  7. Exceptions are mapped over extension of Error enumeration.
  8. Default methods are in extensions implemented.
  9. Swiftify code are implemented in extensions.
  10. All previous points are non-binding recommendations with no binding effect.

How to translate Java source code to Swift

Test it

  • On macOS for

macOS <br/> swift test Linux <br/> only once podman machine init && podman machine start and then to test podman run --rm -v "$(pwd)":/project:ro -w /project swift:latest sh -c "swift test --scratch-path /tmp/build" watchOS <br/> swift test --target JavApi --triple arm64-apple-watchos --sdk $(xcrun --sdk watchos --show-sdk-path) iOS <br/> swift test --target JavApi --triple arm64-apple-ios --sdk $(xcrun --sdk iphoneos --show-sdk-path) visionOS <br/> swift test --target JavApi --triple arm64-apple-xros --sdk $(xcrun --sdk xros --show-sdk-path) tvOS (look for sdk name) <br/> swift build --target JavApi --triple arm64-apple-tvos --sdk $(xcrun --sdk appletvos --show-sdk-path) WASM <br/> once install like Swift.org it describe and then swift build --swift-sdk swift-6.3.2-RELEASE_wasm Android <br/> Install the Android NDK with brew install android-ndk and like Swift.org it describe and then swift test --target JavApi --swift-sdk swift-6.3.2-RELEASE_android

And all together without Windows:

swift test
podman run --rm -v "$(pwd)":/project:ro -w /project swift:latest sh -c "swift test --scratch-path /tmp/build"
swift build --target JavApi --triple arm64-apple-watchos --sdk $(xcrun --sdk watchos --show-sdk-path)
swift build --target JavApi --triple arm64-apple-ios --sdk $(xcrun --sdk iphoneos --show-sdk-path)
xcodebuild build -scheme JavApi -destination 'generic/platform=visionOS' -sdk xros
swift build --target JavApi --triple arm64-apple-tvos --sdk $(xcrun --sdk appletvos --show-sdk-path)
swift build --target JavApi --swift-sdk swift-6.3.2-RELEASE_wasm
swift build --target JavApi --swift-sdk swift-6.3.2-RELEASE_android
swift build --target JavApi --swift-sdk swift-6.3.2-RELEASE_static-linux-0.1.0

<small>Also static Linux are here.</small>

  • On Windows for

* Windows <br/> swift test

Package Metadata

Repository: bastie/javapi4swift

Default branch: main

README: README.md