From f45cebeb3de94a257a29c03bc8e7ca7fd3dcb488 Mon Sep 17 00:00:00 2001 From: Saryu Shah Date: Fri, 13 Oct 2017 14:17:11 +0000 Subject: [PATCH] Updates to policy documentation Updated policy installation documentation ------------------------------------------------------------- Change-Id: I33842f45612a70b29df34db503c8ffbcb12da918 Issue-Id: POLICY-335 Signed-off-by: Saryu Shah --- docs/platform/installation.rst | 25 ++++++++++++++++--------- 1 file changed, 16 insertions(+), 9 deletions(-) diff --git a/docs/platform/installation.rst b/docs/platform/installation.rst index f00066093..a10f02689 100644 --- a/docs/platform/installation.rst +++ b/docs/platform/installation.rst @@ -22,9 +22,9 @@ This procedure assumes that: The procedure documented here has been verified to work on a MacBook laptop running macOS Sierra Version 10.12.6 and a HP Z600 desktop running Ubuntu 16.04.3 LTS. -**Typical ONAP Policy Framework Clone Script** - -.. code-block:: none +.. code-block:: bash + :caption: Typical ONAP Policy Framework Clone Script + :linenos: #!/usr/bin/env bash @@ -152,13 +152,17 @@ Building ONAP * rm -fr ~/.m2/repository/org/onap * rm -fr ~/.m2/repository/org/openecomp + **Step 2**. A pom such as the one below can be used to build all the ONAP policy modules and their dependencies. Create the *pom.xml* file in the directory *~/git/onap*. -**Typical pom.xml to build the ONAP Policy Framework** +.. code-block:: xml + :caption: Typical pom.xml to build the ONAP Policy Framework + :linenos: -.. code-block:: none + - 4.0.0 org.onap onap-policy_standalone @@ -201,11 +205,14 @@ Building ONAP **Step 3**. A pom such as the one below can be used to build the ONAP Policy Framework modules. Create the *pom.xml* file in the directory *~/git/onap/policy* -**Typical pom.xml to build the ONAP Policy Framework Policy Modules** +.. code-block:: xml + :caption: Typical pom.xml to build the ONAP Policy Framework Policy Modules + :linenos: -.. code-block:: none + - 4.0.0 org.onap onap-policy -- 2.16.6