Fix for Gradle logging on asciidoc and swagger generation

2022-06-16 09:19:06 +02:00
parent 3196de0e4d
commit 68fcddf7a7
7 changed files with 46 additions and 42 deletions
@@ -15,14 +15,14 @@ See also: https://gmail.googleblog.com/2009/07/send-mail-from-another-address-wi
 To be able to send emails via SMTP with your GMail account you probably need to create an app password. Please follow these instructions:

 1. Go to your Google Account.
-1. Select Security.
-1. Under "Signing in to Google," select App Passwords. You may need to sign in. If you don't have this option, it might be because:
-1. 2-Step Verification is not set up for your account.
-1. 2-Step Verification is only set up for security keys.
-1. Your account is through work, school, or other organization.
-1. You turned on Advanced Protection.
-1. At the bottom, choose Select app and choose the app you using and then Select device and choose the device you're using and then Generate.
-1. Follow the instructions to enter the App Password. The App Password is the 16-character code in the yellow bar on your device.
-1. Tap Done.
+2. Select Security.
+3. Under "Signing in to Google," select App Passwords. You may need to sign in. If you don't have this option, it might be because:
+4. 2-Step Verification is not set up for your account.
+5. 2-Step Verification is only set up for security keys.
+6. Your account is through work, school, or other organization.
+7. You turned on Advanced Protection.
+8. At the bottom, choose Select app and choose the app you using and then Select device and choose the device you're using and then Generate.
+9. Follow the instructions to enter the App Password. The App Password is the 16-character code in the yellow bar on your device.
+10. Tap Done.

 See also: https://support.google.com/accounts/answer/185833?p=InvalidSecondFactor&visit_id=637856439524128323-869822459&rd=1[Google Support: Sign in with App Passwords] for more details.
@@ -34,7 +34,7 @@ Compression: Uncompressed, ZIP, ZLIB, BZIP2
 +
 CAUTION: The insecure hash algorithm SHA1 is still supported in version 2.2.27. SHA1 is obsolete and you don't want to use it to generate your signature.

-1. Generate your GPG key pair:
+2. Generate your GPG key pair:
 +
 .Input generate GPG key pair
 [source,bash]
@@ -158,21 +158,21 @@ sub rsa2048/4FGHIJ56 2022-04-16 [] [expires: 2024-04-16]
 +
 Now you can find that there are two files created under ~/.gnupg/private-keys-v1.d/ directory. These two files are binary files with .key extension.

-1. Export your public key:
+3. Export your public key:
 +
 [source,bash]
 ----
 gpg --armor --export aleks@apache.org > pubkey.asc
 ----

-1. Export Your Private Key:
+4. Export Your Private Key:
 +
 [source,bash]
 ----
 gpg --export-secret-keys --armor aleks@apache.org > privkey.asc
 ----

-1. Protect Your Private Key and Revocation Certificate
+5. Protect Your Private Key and Revocation Certificate
 +
 Your private key should be kept in a safe place, like an encrypted flash drive. Treat it like your house key. Only you can have it and don't lose it. And you must remember your passphrase, otherwise you can't unlock your private key.
 +
@@ -14,7 +14,7 @@ You do not need to ask committers to hold off any commits until you have branche
 % cd fineract
 ----

-1. Check that current HEAD points to commit on which you want to base new  release branch. Checkout a particular earlier commit if not.
+2. Check that current HEAD points to commit on which you want to base new  release branch. Checkout a particular earlier commit if not.
 +
 [source,bash]
 ----
@@ -22,23 +22,23 @@ You do not need to ask committers to hold off any commits until you have branche
 ----
 <1> Check current branch history. HEAD should point to commit that you want to be base for your release branch

-1. Create a new release branch with name "$Version"
+3. Create a new release branch with name "$Version"
 +
 [source,bash,subs="attributes+,+macros"]
 ----
 % git checkout -b {revnumber}
 ----

-1. Push new branch to Apache Fineract repository
+4. Push new branch to Apache Fineract repository
 +
 [source,bash,subs="attributes+,+macros"]
 ----
 % git push origin {revnumber}
 ----

-1. Add new release notes in Release Folders. The change list can be swiped from the JIRA release note tool (use the "text" format for the change log). See JIRA Cleanup above to ensure that the release notes generated by this tool are what you are expecting.
+5. Add new release notes in Release Folders. The change list can be swiped from the JIRA release note tool (use the "text" format for the change log). See JIRA Cleanup above to ensure that the release notes generated by this tool are what you are expecting.

-1. Send en email announcing the new release branch on the earlier email thread
+6. Send en email announcing the new release branch on the earlier email thread
 +
 [source,text]
 ----