[GH-ISSUE #100] Publish tunnel module to Maven Central #46

New issue

Open

opened 2026-10-13 21:05:31 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-13 21:05:31 +00:00

Owner

Originally created by @DieTime on GitHub (Sep 20, 2026).
Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-android/issues/100

Could the tunnel module be published to Maven Central (or another public Maven repository) as a versioned artifact, e.g. org.amnezia.awg:tunnel?

Upstream WireGuard publishes its tunnel library to Maven Central, which makes adding WireGuard support to an Android app a single dependency line. There is no equivalent for AmneziaWG, so third-party apps have to either vendor this repository as a submodule (pulling in the CMake/Go build chain) or depend on an unofficial forks.

This is blocking real integrations, for example - https://github.com/samosvalishe/turn-proxy-android/pull/60.

That PR adds AmneziaWG support to an Android client, and it stalled on this exact problem. The only AmneziaWG library on Maven is a fork. Its author stopped maintaining it and moved the code into another app, so AWG 3.0 will probably never be added there. There is no official artifact to use instead, so that project's author would have to build the library from source.

If amnezia-vpn published the artifact, other projects would get the library straight from the people who write the protocol, and new protocol versions would reach them as soon as you release them.

Thanks for the work on AmneziaWG.

Originally created by @DieTime on GitHub (Sep 20, 2026). Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-android/issues/100 Could the `tunnel` module be published to Maven Central (or another public Maven repository) as a versioned artifact, e.g. `org.amnezia.awg:tunnel`? Upstream WireGuard publishes its tunnel library to Maven Central, which makes adding WireGuard support to an Android app a single dependency line. There is no equivalent for AmneziaWG, so third-party apps have to either vendor this repository as a submodule (pulling in the CMake/Go build chain) or depend on an unofficial forks. This is blocking real integrations, for example - https://github.com/samosvalishe/turn-proxy-android/pull/60. That PR adds AmneziaWG support to an Android client, and it stalled on this exact problem. The only AmneziaWG library on Maven is a fork. Its author stopped maintaining it and moved the code into another app, so AWG 3.0 will probably never be added there. There is no official artifact to use instead, so that project's author would have to build the library from source. If `amnezia-vpn` published the artifact, other projects would get the library straight from the people who write the protocol, and new protocol versions would reach them as soon as you release them. Thanks for the work on AmneziaWG.

bsakaguchi referenced this issue

2026-10-13 21:05:45 +00:00

[PR #46] [CLOSED] Add connection status notification #66