You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: wiki/Setup-Developer-Workstation.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,31 +25,31 @@ Java keystore is used for signing packages build time.
25
25
26
26
#### Create private key and certificate
27
27
28
-
The process creates an archive called **archetype.keystore-2.1.0** (artefact name + version) containing the generated files (**archetype.keystore**, **cert.pem**, **private_key.pem** ). The archive needs to be deployed on the artefact manager.
28
+
The process creates an archive called **archetype.keystore-1.0.0** (artifact name + version) containing the generated files (**archetype.keystore**, **cert.pem**, **private_key.pem** ). The archive needs to be deployed on the artifact manager.
29
29
30
30
```sh
31
-
mkdir -p ~/cert/archetype.keystore-2.1.0
32
-
cd~/cert/archetype.keystore-2.1.0
31
+
mkdir -p ~/cert/archetype.keystore-1.0.0
32
+
cd~/cert/archetype.keystore-1.0.0
33
33
34
34
## Create the certificates and fill in the required country,state,location,organization details ...
zip archetype.keystore-2.1.0.zip -r archetype.keystore-2.1.0
39
+
zip archetype.keystore-1.0.0.zip -r archetype.keystore-1.0.0
40
40
```
41
41
`Note:` Its very important to note that "Email" field should be EMPTY, otherwise the vRO import will break with 400 OK error
42
42
43
43
`Note:` JKS is a propriatary format specific to the particular JVM provider. When running above commands, ensure the keytool used is the one under the JVM that Maven would use (check with `mvn -v`).
44
44
45
-
#### Deploy the keystore artefact
45
+
#### Deploy the keystore artifact
46
46
47
-
The artefact should be deployed to any path as long as the **settings.xml** file points to it.
47
+
The artifact should be deployed to any path as long as the **settings.xml** file points to it.
48
48
49
49
Example:
50
-
-artefact group ID: com.clientname.build
51
-
-artefact ID: archetype.keystore
52
-
-artefact version: 2.1.0
50
+
-artifact group ID: com.clientname.build
51
+
-artifact ID: archetype.keystore
52
+
-artifact version: 1.0.0
53
53
-**keystorePassword** and **vroKeyPass** passwords need to be replaced with the values used during the key generation process above
0 commit comments