BXMSDOC-3197-master: Update BOM versions in docs. (apache#1060)

tarilabs · Sep 12, 2018 · 4ec9c8e · 4ec9c8e
1 parent 1aa0ed9
commit 4ec9c8e
Show file tree

Hide file tree

Showing 2 changed files with 64 additions and 3 deletions.
diff --git a/drools-docs/src/modules/ROOT/pages/DMN/dmn-invocation-embedded-proc.adoc b/drools-docs/src/modules/ROOT/pages/DMN/dmn-invocation-embedded-proc.adoc
@@ -14,6 +14,8 @@ ifdef::DROOLS,JBPM,OP[]
 <<_builddeployutilizeandrunsection>>.
 endif::[]
 * The following dependencies have been added to the `pom.xml` file of the project:
++
+--
 
 [source,xml,subs="attributes+"]
 ----
@@ -32,7 +34,36 @@ endif::[]
 </dependency>
 ----
 
-NOTE: The `<version>` is the Maven artifact version for {PRODUCT} currently used in your project (for example, {MAVEN_ARTIFACT_VERSION}).
+The `<version>` is the Maven artifact version for {PRODUCT} currently used in your project (for example, {MAVEN_ARTIFACT_VERSION}).
+
+ifdef::DM,PAM[]
+[NOTE]
+====
+Instead of specifying a {PRODUCT} `<version>` for individual dependencies, consider adding the {PRODUCT_BA} bill of materials (BOM) dependency to your project `pom.xml` file. The {PRODUCT_BA} BOM applies to both {PRODUCT_DM} and {PRODUCT_PAM}. When you add the BOM files, the correct versions of transitive dependencies from the provided Maven repositories are included in the project.
+
+Example BOM dependency:
+
+[source,xml,subs="attributes+"]
+----
+<dependency>
+  <groupId>com.redhat.ba</groupId>
+  <artifactId>ba-platform-bom</artifactId>
+  <version>{BOM_VERSION}</version>
+  <scope>import</scope>
+  <type>pom</type>
+</dependency>
+----
+
+For more information about the {PRODUCT_BA} BOM, see
+ifdef::PAM[]
+https://access.redhat.com/solutions/3405361[What is the mapping between RHPAM product and maven library version?].
+endif::[]
+ifdef::DM[]
+https://access.redhat.com/solutions/3363991[What is the mapping between RHDM product and maven library version?].
+endif::[]
+====
+endif::DM,PAM[]
+--
 
 .Procedure
 . Create a KIE container from `classpath` or `ReleaseId`:

diff --git a/drools-docs/src/modules/ROOT/pages/DMN/dmn-invocation-remote-java-proc.adoc b/drools-docs/src/modules/ROOT/pages/DMN/dmn-invocation-remote-java-proc.adoc
@@ -20,7 +20,8 @@ ifdef::DROOLS,JBPM,OP[]
 endif::[]
 * You have the container ID of the KIE container containing the DMN model. If more than one model is present, you must also know the model namespace and model name of the relevant model.
 * The following dependency is added to the `pom.xml` file of the project:
-
++
+--
 [source,xml,subs="attributes+"]
 ----
 <dependency>
@@ -30,7 +31,36 @@ endif::[]
 </dependency>
 ----
 
-NOTE: The `<version>` is the Maven artifact version for {PRODUCT} currently used in your project (for example, {MAVEN_ARTIFACT_VERSION}).
+The `<version>` is the Maven artifact version for {PRODUCT} currently used in your project (for example, {MAVEN_ARTIFACT_VERSION}).
+
+ifdef::DM,PAM[]
+[NOTE]
+====
+Instead of specifying a {PRODUCT} `<version>` for individual dependencies, consider adding the {PRODUCT_BA} bill of materials (BOM) dependency to your project `pom.xml` file. The {PRODUCT_BA} BOM applies to both {PRODUCT_DM} and {PRODUCT_PAM}. When you add the BOM files, the correct versions of transitive dependencies from the provided Maven repositories are included in the project.
+
+Example BOM dependency:
+
+[source,xml,subs="attributes+"]
+----
+<dependency>
+  <groupId>com.redhat.ba</groupId>
+  <artifactId>ba-platform-bom</artifactId>
+  <version>{BOM_VERSION}</version>
+  <scope>import</scope>
+  <type>pom</type>
+</dependency>
+----
+
+For more information about the {PRODUCT_BA} BOM, see
+ifdef::PAM[]
+https://access.redhat.com/solutions/3405361[What is the mapping between RHPAM product and maven library version?].
+endif::[]
+ifdef::DM[]
+https://access.redhat.com/solutions/3363991[What is the mapping between RHDM product and maven library version?].
+endif::[]
+====
+endif::DM,PAM[]
+--
 
 .Procedure
 . Instantiate a `KieServicesClient` instance with the appropriate connection information.