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: README.md
-53Lines changed: 0 additions & 53 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -457,59 +457,6 @@ Upgrades sometimes require package name changes. Changed code should ideally ha
457
457
Our `ClasspathHellDuplicatesCheckRuleTest` detects classes that appear in more than 1 JAR. If a version bump in [`build.gradle`](https://github.com/search?q=repo%3Aapache%2Ffineract+filename%3Abuild.gradle&type=Code&ref=advsearch&l=&l=) causes changes in transitives dependencies, then you may have to add related `exclude` to our [`dependencies.gradle`](https://github.com/apache/fineract/search?q=dependencies.gradle). Running `./gradlew dependencies` helps to understand what is required.
458
458
459
459
460
-
Releasing
461
-
---------
462
-
463
-
[How to Release Apache Fineract](https://cwiki.apache.org/confluence/x/DRwIB) documents the process how we make the source code that is available here in this Git repository into a binary release tar.gz available on http://fineract.apache.org.
464
-
465
-
Before you use Gradle to create a release you need to make sure that you provide the proper GPG parameters. You have to options:
466
-
467
-
1. Provide the parameters via ~/.gradle/gradle.properties in your home folder:
468
-
```
469
-
signing.gnupg.keyName=7890ABCD
470
-
signing.gnupg.passphrase=secret
471
-
```
472
-
473
-
IMPORTANT: Do not set your GPG secrets in one of the project gradle.properties and double check that you are not accidentally committing them to Git.
474
-
475
-
The release command would look then look like this:
476
-
```
477
-
./gradlew -Pfineract.release clean build
478
-
```
479
-
480
-
2. Another way to provide these parameters are via project parameters on the command line. A release command would then look like this:
NOTE: Let's assume your GPG key ID would be "ABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890ABCD" then you have to use the last 8 characters (i. e. "7890ABCD") for the signing plugin property "signing.gnupg.keyName".
486
-
487
-
Above tasks will create the following files in folder build/distributions:
488
-
489
-
- binary distribution file: apache-fineract-1.6.0-binary.tar.gz
490
-
- ASCII armored signature for binary distribution: apache-fineract-1.6.0-binary.tar.gz.asc
491
-
- SHA512 checksum for binary distribution: apache-fineract-1.6.0-binary.tar.gz.sha512
492
-
- source distribution file: apache-fineract-1.6.0-src.tar.gz
493
-
- ASCII armored signature for source distribution: apache-fineract-1.6.0-src.tar.gz.asc
494
-
- SHA512 checksum for source distribution: apache-fineract-1.6.0-src.tar.gz.sha512
495
-
496
-
The signatures are automatically verified by the build script. It will throw an exception if the verification fails.
497
-
498
-
Additionally, you can verify the validity of the release distribution files e. g. with:
0 commit comments