Future of this project

[tomsiewert]

Most of you have already seen from the commits, as well as from the time I needed for the issues, that the project here is relatively unmaintained from my side. I would like to explain why this is so, as the client is used more than I thought.

I started the project when I was still in school and had a lot of free time. I spent this free time, besides friends and family, almost exclusively with Java.
Since I started my apprenticeship at Hetzner, the contact with Java has decreased, because we don't use this language internally, as well as my available free time. I concentrate more on my work and the training itself, as well as I try to use my little free time as much as possible, but with friends and family instead of with an IDE.

However, when I do some programming, I do it in languages like Golang or Ruby. Java is rarely used here, mostly only through vocational school.

I would not like to drop this project, as it is (apparently) the only Java client that is largely well maintained (even if everything takes some time to implement).

I would also like to point out that I am happy to accept help from anyone, be it as PR or as a simple issue.

Thank you for your understanding.

[pellepelster]

Hey, would you be ok with replacing Spring with a more lightweight HTTP only library (e.g. OkHttp)?

Currently only the Resttemplate is used from Spring, which in my opinion drags in a lot of complexity and dependencies just to execute some basic HTTP requests. Spring, being a fairly complex piece of software with a lot of dependencies also greatly increases the attack surface (see CVEs for currently used version) and makes usage in a Spring application potentially harder.

[tomsiewert]

I would be okay with replacing Spring completely.

[Griefed]

Moin tomsiewert,

I'm currently exploring the possibilities of working with your hetznercloud-api and noticed that only versions up to 2.13.0 are available on Maven. However, the latest release here on GitHub is 2.15.1.

Have you discontinued publishing to Maven?

Thanks for all the work you've put into this project and I hope all is well over at ye olde Hetzner HQ. 🙂

Cheers,
Griefed

[tomsiewert]

That's odd. I deployed 2.15.1 and 2.15.0 to central maven (see https://github.com/tomsiewert/hetznercloud-java/runs/6666766826?check_suite_focus=true) 🤔
Will investigate this later.

[tomsiewert]

I found the issue. It was stuck in OSS staging. I will investigate this further and add some fixes to release it completely via GH Actions.

For now, I published 2.15.1 manually.

[tomsiewert]

Automatic publishing should work again. There was a bug in the nexus-staging-plugin which did not automatically close the staging repository.

I've uploaded the missing versions manually.

[Griefed]

Thank you very much! Very much looking forward to using the newer version.
I'm having great fun working with your library, thank you very much for all your hard work. 🙂

Beste Grüße 👋
Griefed

[tomsiewert]

After nearly half a year of silence, I've published 3.0.0 today which includes the migration from Spring to OkHttp, flexible networks options, firewalls and more.

Big Thanks to @pellepelster and @Kryp7x for contributing the main changes in v3.0.0.

[pellepelster]

What a great christmas present, thanks a lot!