Bump org.zeromq:jeromq from 0.5.4 to 0.6.0

[dependabot]

Bumps org.zeromq:jeromq from 0.5.4 to 0.6.0.

Changelog

Sourced from org.zeromq:jeromq's changelog.

v0.6.0 (2024-02-04)

Added

• #964 zeromq/jeromq#964 Exports all options default values as constant in ZMQ class. This will allow client libraries to use them.

• #963 (zeromq/jeromq#963) Replaces maven-bundle-plugin with the more up-to-date bnd-maven-plugin and configures it to generate a JPMS module descriptor besides the OSGi descriptor.

• #949 (zeromq/jeromq#949) Added a way to specify a custom monitor, that don’t need to communicate through a ZMQ socket. It allows to use monitor for logging without hitting hard on the CPU with poller overload. Improved in #950 (zeromq/jeromq#950)

• #942 (zeromq/jeromq#942) zmq.Ctx can now be provided a thread factory, that can used to tweaks threads. The main purpose of this is to be able to bind thread to CPU using external libraries like https://github.com/OpenHFT/Java-Thread-Affinity. The idea was suggested by issue #910.

• Also adding a check that prevent modifications of some settings once they have been used by zmq.Ctx initialisation.

Changed

• Many code smell removed using SonarLint.

• #941 (zeromq/jeromq#940) Fix to issue #940 by setting `key=null on setKey, added test

• #939 (zeromq/jeromq#939) Simplified Mailbox, always thread safe, so `MailboxSafe usages are removed and the class is marked at deprecated.

• #936 (zeromq/jeromq#936)

  org.zeromq.ZSocket and org.zeromq.ZMQ.Socket can now read and write zmq.Msg directly.

  Updating Metada class to provide more data access and functions. ZMetadata is updated too. It internally now uses ConcurrentHashMap instead of the old Properties class. The Properties class ignore null values, ConcurrentHashMap reject them but ZMTP protocol allows empty values. So null values are transformed to empty strings.

  Metada#set is deprecated and replaced by Metada#put, to be more consistent with Map API.

  Lots of hostile final method declaration removed.

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[vy]

@dependabot rebase

[ppkarwasz]

The change in module name was addressed here: 090123c

[vy]

The change in module name was addressed here: 090123c

How did you notice the change?

[ppkarwasz]

I am the one that submitted the PR to JeroMQ that adds a real module descriptor.