This is an automated email from the ASF dual-hosted git repository.
jhelou pushed a change to branch pulsar-authentication
in repository https://gitbox.apache.org/repos/asf/james-project.git
omit 3e2c33cca3 [JAMES-3687] refactors client creation to
PulsarConfiguration
omit a2ca77601d [JAMES-3687] adds support for authentication scheme in the
configuration
omit 01e9ef7a7e [JAMES-3687] pulls pulsar-client explicitely to enforce its
version
add fdbdfc808b [JAMES-3687] pulls pulsar-client explicitely to enforce its
version
add bcc6c9f383 [JAMES-3687] adds support for authentication scheme in the
configuration
add 69617a064a [JAMES-3687] refactors client creation to
PulsarConfiguration
add 2b6bdf541d [JAMES-3687] upgrades pulsar client to latest version
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (3e2c33cca3)
\
N -- N -- N refs/heads/pulsar-authentication (2b6bdf541d)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
backends-common/pulsar/pom.xml | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
