I think it's worth to be listed because it has a completely different approach than the other Java clients that are available on the market:
it is lightweight (only 2 transitive dependencies, both optional in some cases)
it can communicate with both a local Docker (via Unix sockets) as well as a remote one.
it is 100% encapsulated (it's an API, not an SDK)
it is extensible since everything happens via interfaces -- only 2 public entry points and from there the user works only with Java interfaces which they can decorate.
any version of Docker's API can be used, either trough interfaces or by using the HttpClient directly, since we do not provide animating models, only JsonObjects.
high test coverage and strict quality control (see how we use Rultor in order to keep the master branch read-only,
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/veggiemonk/awesome-docker/pull/644
**Author:** [@amihaiemil](https://github.com/amihaiemil)
**Created:** 12/10/2018
**Status:** ✅ Merged
**Merged:** 12/15/2018
**Merged by:** [@veggiemonk](https://github.com/veggiemonk)
**Base:** `master` ← **Head:** `master`
---
### 📝 Commits (1)
- [`bb7a45e`](https://github.com/veggiemonk/awesome-docker/commit/bb7a45e701d1765afea0396c482d20bf8ef8e49f) Added docker-java-api
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+1 -0)
</details>
### 📄 Description
Added this library: https://github.com/amihaiemil/docker-java-api
I think it's worth to be listed because it has a completely different approach than the other Java clients that are available on the market:
* it is lightweight (only 2 transitive dependencies, both optional in some cases)
* it can communicate with both a local Docker (via Unix sockets) as well as a remote one.
* it is 100% encapsulated (it's an API, not an SDK)
* it is extensible since everything happens via interfaces -- only 2 public entry points and from there the user works only with Java interfaces which they can decorate.
* any version of Docker's API can be used, either trough interfaces or by using the ``HttpClient`` directly, since we do not provide animating models, only JsonObjects.
* high test coverage and strict quality control (see how we use [Rultor](http://www.rultor.com) in order to keep the master branch read-only,
* innovative project management via [Zerocracy](https://www.zerocracy.com).
You can also read the [motivational blog post](https://www.amihaiemil.com/2018/03/10/java-api-for-docker.html).
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/veggiemonk/awesome-docker/pull/644
Author: @amihaiemil
Created: 12/10/2018
Status: ✅ Merged
Merged: 12/15/2018
Merged by: @veggiemonk
Base:
master← Head:master📝 Commits (1)
bb7a45eAdded docker-java-api📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
README.md(+1 -0)📄 Description
Added this library: https://github.com/amihaiemil/docker-java-api
I think it's worth to be listed because it has a completely different approach than the other Java clients that are available on the market:
HttpClientdirectly, since we do not provide animating models, only JsonObjects.You can also read the motivational blog post.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.