Procedure for creating custom vropkg sign certificate#117
Conversation
|
@llyubenova, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
wiki/Setup-Developer-Workstation.md
Outdated
|
|
||
| `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`). | ||
| Example: | ||
| - artefact group ID: com.clientname.build |
There was a problem hiding this comment.
Just a small typo, should be artifact
wiki/Setup-Developer-Workstation.md
Outdated
| # Generate new Key | ||
| keytool -genkey -keyalg RSA -keysize 2048 -alias _dunesrsa_alias_ -keystore package.jks -storepass 'VMware1!' -validity 3650 -dname 'CN=Project,OU=Department,O=Company,L=City,ST=State,C=XX,emailAddress=administrator@vsphere.local' | ||
| ```sh | ||
| mkdir -p ~/cert/archetype.keystore-2.1.0 |
There was a problem hiding this comment.
Lets give the example with version 1.0.0
|
@llyubenova, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
|
@llyubenova, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding
|
Signed-off-by: Liliya Lyubenova <llyubenova@vmware.com>
9f02720 to
6297c66
Compare
Description
Described procedure for creating custom vropkg sign certificate
Checklist
Fixed #XXX -orClosed #XXX -prefix to auto-close the issueTesting
Release Notes
Screenshot
Related issues and PRs