From 1e8d0c326071c4a3b0b8bce1b8040b056a7bca26 Mon Sep 17 00:00:00 2001 From: bigmarvin Date: Mon, 20 Apr 2020 16:00:48 +0800 Subject: [PATCH] [CURATOR-464] update classifier and document accordingly --- pom.xml | 2 +- src/site/confluence/index.confluence | 4 ++++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/pom.xml b/pom.xml index 427037f146..df45a2e676 100644 --- a/pom.xml +++ b/pom.xml @@ -971,7 +971,7 @@ ${project.build.directory}/original-${project.build.finalName}.jar jar - original + osgi ${skip-attaching-original-artifact} diff --git a/src/site/confluence/index.confluence b/src/site/confluence/index.confluence index 431acbede5..8ea1c0e30b 100644 --- a/src/site/confluence/index.confluence +++ b/src/site/confluence/index.confluence @@ -35,6 +35,10 @@ h2. Maven / Artifacts Curator binaries are published to Maven Central. Curator consists of several artifacts. Which artifacts to use depends on your needs. For most users, the only artifact you need is curator\-recipes. +For OSGi users, there's another set of artifacts of classifier osgi available in Maven Central. These artifacts are not +shaded, thus no package relocation is performed inside, so hopefully they could start as bundles when their dependencies +are fulfilled by dedicated bundles, e.g. guava. + ||GroupID/Org||ArtifactID/Name||Description|| |org.apache.curator|curator\-recipes|All of the recipes. Note: this artifact has dependencies on client and framework and, so, Maven (or whatever tool you're using) should pull those in automatically.| |org.apache.curator|curator\-async|Asynchronous DSL with O/R modeling, migrations and many other features.|