CORDA-2491: Ability to specify Java package namespace from Cordform (#5075)

Add entry point with generic extra configuration options. Move configuration verification code to avoid circular dependencies.

docs/source/changelog.rst

@@ -14,6 +14,9 @@ Version 4.2
   of a contract without having to manually install that version, provided a newer version is installed. Similarly, non-contract attachments
   are whitelisted if another attachment is present on the node that is signed by the same public key.
 
+* :doc:`design/data-model-upgrades/package-namespace-ownership` configurations can be now be set as described in
+  :ref:`node_package_namespace_ownership`, when using the Cordformation plugin version 4.0.43.
+
 .. _changelog_v4.0:
 
 Version 4.0

docs/source/generating-a-node.rst

@@ -143,6 +143,29 @@ To copy the same file to all nodes `ext.drivers` can be defined in the top level
         }
     }
 
+.. _node_package_namespace_ownership:
+
+Package namespace ownership
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+To specify :doc:`design/data-model-upgrades/package-namespace-ownership` configuration, the optional ``networkParameterOverrides`` and ``packageOwnership`` blocks can be used, similar to the configuration file used in :doc:`network-bootstrapper`:
+
+.. sourcecode:: groovy
+
+    task deployNodes(type: net.corda.plugins.Cordform, dependsOn: ['jar']) {
+        [...]
+        networkParameterOverrides {
+            packageOwnership {
+                "com.mypackagename" {
+                    keystore = "_teststore"
+                    keystorePassword = "MyStorePassword"
+                    keystoreAlias = "MyKeyAlias"
+                }
+            }
+        }
+        [...]
+    }
+
+
 Signing Cordapp JARs
 ^^^^^^^^^^^^^^^^^^^^
 The default behaviour of Cordform is to deploy CorDapp JARs "as built":