This is an automated email from the ASF dual-hosted git repository.
urfree pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
The following commit(s) were added to refs/heads/main by this push:
new 3f286ef Docs sync done from apache/pulsar(#7c1f17a)
3f286ef is described below
commit 3f286efb802fe615bc60cb2ed3291c7955c0822c
Author: Pulsar Site Updater <[email protected]>
AuthorDate: Wed Mar 9 06:02:39 2022 +0000
Docs sync done from apache/pulsar(#7c1f17a)
---
site2/docs/client-libraries-java.md | 7 ++++++-
site2/website-next/docs/client-libraries-java.md | 9 ++++++++-
.../versioned_docs/version-2.2.0/client-libraries-java.md | 9 ++++++++-
.../versioned_docs/version-2.3.0/client-libraries-java.md | 9 ++++++++-
.../versioned_docs/version-2.3.2/client-libraries-java.md | 9 ++++++++-
5 files changed, 38 insertions(+), 5 deletions(-)
diff --git a/site2/docs/client-libraries-java.md
b/site2/docs/client-libraries-java.md
index 59fc715..a275ff4 100644
--- a/site2/docs/client-libraries-java.md
+++ b/site2/docs/client-libraries-java.md
@@ -12,7 +12,7 @@ Javadoc for the Pulsar client is divided into two domains by
package as follows.
Package | Description | Maven Artifact
:-------|:------------|:--------------
-[`org.apache.pulsar.client.api`](/api/client) | The producer and consumer API
|
[org.apache.pulsar:pulsar-client:{{pulsar:version}}](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client%7C{{pulsar:version}}%7Cjar)
+[`org.apache.pulsar.client.api`](/api/client) | [The producer and consumer
API](https://pulsar.apache.org/api/client/) |
[org.apache.pulsar:pulsar-client:{{pulsar:version}}](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client%7C{{pulsar:version}}%7Cjar)
[`org.apache.pulsar.client.admin`](/api/admin) | The Java [admin
API](admin-api-overview.md) |
[org.apache.pulsar:pulsar-client-admin:{{pulsar:version}}](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client-admin%7C{{pulsar:version}}%7Cjar)
`org.apache.pulsar.client.all` |Include both `pulsar-client` and
`pulsar-client-admin`<br /> Both `pulsar-client` and `pulsar-client-admin` are
shaded packages and they shade dependencies independently. Consequently, the
applications using both `pulsar-client` and `pulsar-client-admin` have
redundant shaded classes. It would be troublesome if you introduce new
dependencies but forget to update shading rules. <br /> In this case, you can
use `pulsar-client-all`, which shades dependencies [...]
@@ -22,6 +22,11 @@ This document focuses only on the client API for producing
and consuming message
The latest version of the Pulsar Java client library is available via [Maven
Central](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client%7C{{pulsar:version}}%7Cjar).
To use the latest version, add the `pulsar-client` library to your build
configuration.
+> **Tip**
+>
+> -
[`pulsar-client`](https://search.maven.org/artifact/org.apache.pulsar/pulsar-client)
and
[`pulsar-client-admin`](https://search.maven.org/artifact/org.apache.pulsar/pulsar-client-admin)
shade dependencies via
[maven-shade-plugin](https://maven.apache.org/plugins/maven-shade-plugin/) to
avoid conflicts of the underlying dependency packages (such as Netty). If you
do not want to manage dependency conflicts manually, you can use them.
+>
+> -
[`pulsar-client-original`](https://search.maven.org/artifact/org.apache.pulsar/pulsar-client-original)
and
[`pulsar-client-admin-original`](https://search.maven.org/artifact/org.apache.pulsar/pulsar-client-admin-original)
**does not** shade dependencies. If you want to manage dependencies manually,
you can use them.
### Maven
If you use Maven, add the following information to the `pom.xml` file.
diff --git a/site2/website-next/docs/client-libraries-java.md
b/site2/website-next/docs/client-libraries-java.md
index a0c4f98..c07d7f7 100644
--- a/site2/website-next/docs/client-libraries-java.md
+++ b/site2/website-next/docs/client-libraries-java.md
@@ -18,7 +18,7 @@ Javadoc for the Pulsar client is divided into two domains by
package as follows.
Package | Description | Maven Artifact
:-------|:------------|:--------------
-[`org.apache.pulsar.client.api`](/api/client) | The producer and consumer API
|
[org.apache.pulsar:pulsar-client:@pulsar:version@](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client%7C@pulsar:version@%7Cjar)
+[`org.apache.pulsar.client.api`](/api/client) | [The producer and consumer
API](https://pulsar.apache.org/api/client/) |
[org.apache.pulsar:pulsar-client:@pulsar:version@](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client%7C@pulsar:version@%7Cjar)
[`org.apache.pulsar.client.admin`](/api/admin) | The Java [admin
API](admin-api-overview) |
[org.apache.pulsar:pulsar-client-admin:@pulsar:version@](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client-admin%7C@pulsar:version@%7Cjar)
`org.apache.pulsar.client.all` |Include both `pulsar-client` and
`pulsar-client-admin`<br /> Both `pulsar-client` and `pulsar-client-admin` are
shaded packages and they shade dependencies independently. Consequently, the
applications using both `pulsar-client` and `pulsar-client-admin` have
redundant shaded classes. It would be troublesome if you introduce new
dependencies but forget to update shading rules. <br /> In this case, you can
use `pulsar-client-all`, which shades dependencies [...]
@@ -28,6 +28,13 @@ This document focuses only on the client API for producing
and consuming message
The latest version of the Pulsar Java client library is available via [Maven
Central](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client%7C@pulsar:version@%7Cjar).
To use the latest version, add the `pulsar-client` library to your build
configuration.
+:::tip
+
+-
[`pulsar-client`](https://search.maven.org/artifact/org.apache.pulsar/pulsar-client)
and
[`pulsar-client-admin`](https://search.maven.org/artifact/org.apache.pulsar/pulsar-client-admin)
shade dependencies via
[maven-shade-plugin](https://maven.apache.org/plugins/maven-shade-plugin/) to
avoid conflicts of the underlying dependency packages (such as Netty). If you
do not want to manage dependency conflicts manually, you can use them.
+-
[`pulsar-client-original`](https://search.maven.org/artifact/org.apache.pulsar/pulsar-client-original)
and
[`pulsar-client-admin-original`](https://search.maven.org/artifact/org.apache.pulsar/pulsar-client-admin-original)
**does not** shade dependencies. If you want to manage dependencies manually,
you can use them.
+
+:::
+
### Maven
If you use Maven, add the following information to the `pom.xml` file.
diff --git
a/site2/website-next/versioned_docs/version-2.2.0/client-libraries-java.md
b/site2/website-next/versioned_docs/version-2.2.0/client-libraries-java.md
index a0c4f98..c07d7f7 100644
--- a/site2/website-next/versioned_docs/version-2.2.0/client-libraries-java.md
+++ b/site2/website-next/versioned_docs/version-2.2.0/client-libraries-java.md
@@ -18,7 +18,7 @@ Javadoc for the Pulsar client is divided into two domains by
package as follows.
Package | Description | Maven Artifact
:-------|:------------|:--------------
-[`org.apache.pulsar.client.api`](/api/client) | The producer and consumer API
|
[org.apache.pulsar:pulsar-client:@pulsar:version@](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client%7C@pulsar:version@%7Cjar)
+[`org.apache.pulsar.client.api`](/api/client) | [The producer and consumer
API](https://pulsar.apache.org/api/client/) |
[org.apache.pulsar:pulsar-client:@pulsar:version@](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client%7C@pulsar:version@%7Cjar)
[`org.apache.pulsar.client.admin`](/api/admin) | The Java [admin
API](admin-api-overview) |
[org.apache.pulsar:pulsar-client-admin:@pulsar:version@](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client-admin%7C@pulsar:version@%7Cjar)
`org.apache.pulsar.client.all` |Include both `pulsar-client` and
`pulsar-client-admin`<br /> Both `pulsar-client` and `pulsar-client-admin` are
shaded packages and they shade dependencies independently. Consequently, the
applications using both `pulsar-client` and `pulsar-client-admin` have
redundant shaded classes. It would be troublesome if you introduce new
dependencies but forget to update shading rules. <br /> In this case, you can
use `pulsar-client-all`, which shades dependencies [...]
@@ -28,6 +28,13 @@ This document focuses only on the client API for producing
and consuming message
The latest version of the Pulsar Java client library is available via [Maven
Central](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client%7C@pulsar:version@%7Cjar).
To use the latest version, add the `pulsar-client` library to your build
configuration.
+:::tip
+
+-
[`pulsar-client`](https://search.maven.org/artifact/org.apache.pulsar/pulsar-client)
and
[`pulsar-client-admin`](https://search.maven.org/artifact/org.apache.pulsar/pulsar-client-admin)
shade dependencies via
[maven-shade-plugin](https://maven.apache.org/plugins/maven-shade-plugin/) to
avoid conflicts of the underlying dependency packages (such as Netty). If you
do not want to manage dependency conflicts manually, you can use them.
+-
[`pulsar-client-original`](https://search.maven.org/artifact/org.apache.pulsar/pulsar-client-original)
and
[`pulsar-client-admin-original`](https://search.maven.org/artifact/org.apache.pulsar/pulsar-client-admin-original)
**does not** shade dependencies. If you want to manage dependencies manually,
you can use them.
+
+:::
+
### Maven
If you use Maven, add the following information to the `pom.xml` file.
diff --git
a/site2/website-next/versioned_docs/version-2.3.0/client-libraries-java.md
b/site2/website-next/versioned_docs/version-2.3.0/client-libraries-java.md
index a0c4f98..c07d7f7 100644
--- a/site2/website-next/versioned_docs/version-2.3.0/client-libraries-java.md
+++ b/site2/website-next/versioned_docs/version-2.3.0/client-libraries-java.md
@@ -18,7 +18,7 @@ Javadoc for the Pulsar client is divided into two domains by
package as follows.
Package | Description | Maven Artifact
:-------|:------------|:--------------
-[`org.apache.pulsar.client.api`](/api/client) | The producer and consumer API
|
[org.apache.pulsar:pulsar-client:@pulsar:version@](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client%7C@pulsar:version@%7Cjar)
+[`org.apache.pulsar.client.api`](/api/client) | [The producer and consumer
API](https://pulsar.apache.org/api/client/) |
[org.apache.pulsar:pulsar-client:@pulsar:version@](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client%7C@pulsar:version@%7Cjar)
[`org.apache.pulsar.client.admin`](/api/admin) | The Java [admin
API](admin-api-overview) |
[org.apache.pulsar:pulsar-client-admin:@pulsar:version@](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client-admin%7C@pulsar:version@%7Cjar)
`org.apache.pulsar.client.all` |Include both `pulsar-client` and
`pulsar-client-admin`<br /> Both `pulsar-client` and `pulsar-client-admin` are
shaded packages and they shade dependencies independently. Consequently, the
applications using both `pulsar-client` and `pulsar-client-admin` have
redundant shaded classes. It would be troublesome if you introduce new
dependencies but forget to update shading rules. <br /> In this case, you can
use `pulsar-client-all`, which shades dependencies [...]
@@ -28,6 +28,13 @@ This document focuses only on the client API for producing
and consuming message
The latest version of the Pulsar Java client library is available via [Maven
Central](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client%7C@pulsar:version@%7Cjar).
To use the latest version, add the `pulsar-client` library to your build
configuration.
+:::tip
+
+-
[`pulsar-client`](https://search.maven.org/artifact/org.apache.pulsar/pulsar-client)
and
[`pulsar-client-admin`](https://search.maven.org/artifact/org.apache.pulsar/pulsar-client-admin)
shade dependencies via
[maven-shade-plugin](https://maven.apache.org/plugins/maven-shade-plugin/) to
avoid conflicts of the underlying dependency packages (such as Netty). If you
do not want to manage dependency conflicts manually, you can use them.
+-
[`pulsar-client-original`](https://search.maven.org/artifact/org.apache.pulsar/pulsar-client-original)
and
[`pulsar-client-admin-original`](https://search.maven.org/artifact/org.apache.pulsar/pulsar-client-admin-original)
**does not** shade dependencies. If you want to manage dependencies manually,
you can use them.
+
+:::
+
### Maven
If you use Maven, add the following information to the `pom.xml` file.
diff --git
a/site2/website-next/versioned_docs/version-2.3.2/client-libraries-java.md
b/site2/website-next/versioned_docs/version-2.3.2/client-libraries-java.md
index a0c4f98..c07d7f7 100644
--- a/site2/website-next/versioned_docs/version-2.3.2/client-libraries-java.md
+++ b/site2/website-next/versioned_docs/version-2.3.2/client-libraries-java.md
@@ -18,7 +18,7 @@ Javadoc for the Pulsar client is divided into two domains by
package as follows.
Package | Description | Maven Artifact
:-------|:------------|:--------------
-[`org.apache.pulsar.client.api`](/api/client) | The producer and consumer API
|
[org.apache.pulsar:pulsar-client:@pulsar:version@](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client%7C@pulsar:version@%7Cjar)
+[`org.apache.pulsar.client.api`](/api/client) | [The producer and consumer
API](https://pulsar.apache.org/api/client/) |
[org.apache.pulsar:pulsar-client:@pulsar:version@](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client%7C@pulsar:version@%7Cjar)
[`org.apache.pulsar.client.admin`](/api/admin) | The Java [admin
API](admin-api-overview) |
[org.apache.pulsar:pulsar-client-admin:@pulsar:version@](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client-admin%7C@pulsar:version@%7Cjar)
`org.apache.pulsar.client.all` |Include both `pulsar-client` and
`pulsar-client-admin`<br /> Both `pulsar-client` and `pulsar-client-admin` are
shaded packages and they shade dependencies independently. Consequently, the
applications using both `pulsar-client` and `pulsar-client-admin` have
redundant shaded classes. It would be troublesome if you introduce new
dependencies but forget to update shading rules. <br /> In this case, you can
use `pulsar-client-all`, which shades dependencies [...]
@@ -28,6 +28,13 @@ This document focuses only on the client API for producing
and consuming message
The latest version of the Pulsar Java client library is available via [Maven
Central](http://search.maven.org/#artifactdetails%7Corg.apache.pulsar%7Cpulsar-client%7C@pulsar:version@%7Cjar).
To use the latest version, add the `pulsar-client` library to your build
configuration.
+:::tip
+
+-
[`pulsar-client`](https://search.maven.org/artifact/org.apache.pulsar/pulsar-client)
and
[`pulsar-client-admin`](https://search.maven.org/artifact/org.apache.pulsar/pulsar-client-admin)
shade dependencies via
[maven-shade-plugin](https://maven.apache.org/plugins/maven-shade-plugin/) to
avoid conflicts of the underlying dependency packages (such as Netty). If you
do not want to manage dependency conflicts manually, you can use them.
+-
[`pulsar-client-original`](https://search.maven.org/artifact/org.apache.pulsar/pulsar-client-original)
and
[`pulsar-client-admin-original`](https://search.maven.org/artifact/org.apache.pulsar/pulsar-client-admin-original)
**does not** shade dependencies. If you want to manage dependencies manually,
you can use them.
+
+:::
+
### Maven
If you use Maven, add the following information to the `pom.xml` file.
