I not have any changes which were not pushed to Socks5 proxy component. Most likely I made a mistake and updated dependency in Tigase XMPP Server where there was no need to do so.

Change was introduced in 76363c01ee055e175272ff8f374298edcb151aed which was related to #4468 - creating http-api documentation

I've switched to latest released version (we should used latest released version unless there are any commits made that would validate switching to SNAPSHOT!)

-			<version>1.3.0-SNAPSHOT</version>
+			<version>1.2.0</version>

Thank you for looking into this. However, I still have one concern about this and possibly other projects related to the Tigase XMPP Server. It appears that the current snapshot version of the socks5 proxy component still depends on the Tigase XMPP Server version 7.1.0. I am worried that due to major API changes in the Tigase XMPP Server 7.2.0 the socks5 proxy component may not work with the new version if the code (API compatibility issues) if the code still depends on server 7.1.0.

Maybe we should bump major version of all components and make them dependent on the server version 7.2.0-SNAPSHOT to make sure they will work correctly with the final 7.2.0?

Artur Hefczyc wrote:

Maybe we should bump major version of all components and make them dependent on the server version 7.2.0-SNAPSHOT to make sure they will work correctly with the final 7.2.0?

Almost all components follows this - master depends on the latest 7.2.0-SNAPSHOT version, stable on 7.1.0 (in this case there shouldn't be any API changes!) and old-stable on @5.2.0@. I've updated Socks5 and STUN components to match this schema (mast have slipped when making release).

Ok, that makes sense.