Any chance you'll use mvnrepository.com?

[acloudmovingby]

Hi Jon5477!

Thanks for making this fork. Your improvements make a lot of sense, in particular actually implementing ACL tokens properly and moving away from Apache http client.

I'm having trouble using your Maven snippets (from the wiki) since it seems our corporate VPN is blocking me from downloading from the repository. I'll try to get around that and/or build from source myself, but any chance this will get added to mvnrepository.com?

Thanks again!

--Chris

[jon5477]

Yeah, I can start looking into it. Thanks for sharing your specific use case. I'll close this issue once we have this artifact uploaded to maven central. Please keep in mind that I haven't made a full release yet and it is still a snapshot version, would you require a release anytime soon?

[acloudmovingby]

Hi @jon5477, not an urgent need. Worst case scenario, we may make our own fork temporarily. Any goals you're working on to get to a full release?

[jon5477]

@acloudmovingby There is a goal to get it to a stable release version, I just need some feedback from users of the library before I perform a release. It'll be in the plans to release it to Maven Central since I also use this in production. Keep me posted if there are any potential issues in the latest snapshot. Thanks

[oliverlockwood]

@jon5477 Thank you very much for taking on the maintenance of this library and dealing with some of the backlog of issues, particularly regarding how Consul tokens are provided to the server.

While it's possible to use this by adding an additional Maven repository, specifically https://maven.pkg.github.com/jon5477/consul-api, It'd be good for this to be made available on Maven Central if it's not too much hassle for you. Thanks again.

[yeroc]

@jon5477 I'm wondering whether this is still on your radar, or is this fork no longer being maintained? I was looking for a replacement for the ekwid library and found your fork but will keep looking if you don't intend to publish to Maven Central anymore.

[oliverlockwood]

@yeroc FYI, after initially trying to migrate from ecwid:consul-api to this library, we found that there were a bunch of things were it wasn't up to scratch for our use-case - some of the operations still pass a consul token in a token query parameter instead of an X-Consul-Token header.

We've created https://github.com/dalet-oss/consul-api/ which is forked from the original library, with one of jon5477's changes cherry-picked, and our own implementation of ensuring tokens are always sent as headers. It's published to Maven Central, and you're welcome to make use of it if it helps you.

[corey-kdm]

Thanks @oliverlockwood. I noticed your fork requires Java 17. We're still stuck on Java 11 for the moment so can't use yours unfortunately.

[oliverlockwood]

@corey-kdm ask and you shall receive 😇
dalet-oss@1940471
(There was actually no particular reason to restrict to Java 17+, except syntactic sugar, and not a lot even of that.)

Version 1.5.1 is now available on Maven Central, and this is compiled to be compatible with Java 11.

Hope it helps you out. If you have any more issues, feel free to raise them at https://github.com/dalet-oss/consul-api/issues.