This is an automated email from the ASF dual-hosted git repository. meonkeys pushed a commit to branch fix-tarball-naming in repository https://gitbox.apache.org/repos/asf/fineract.git
commit a649db6dd8fb229aff4ea6459e9d2cd7d1d2d484 Author: Adam Monsen <[email protected]> AuthorDate: Sun Jul 27 20:54:31 2025 -0700 FINERACT-2335: don't rename release tarballs Release tarballs are currently renamed (without changing the contents): apache-fineract-src-1.12.1.tar.gz becomes apache-fineract-1.12.1-src.tar.gz . The former matches the exploded directory name, the latter does not. The difference is subtle but meaningful... I strongly prefer the former because it's less surprising / more common, and easier to work with from scripts. There's no functional difference, this should only impact aesthetics. --- fineract-war/build.gradle | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/fineract-war/build.gradle b/fineract-war/build.gradle index 93b12e4226..60a5bc6186 100644 --- a/fineract-war/build.gradle +++ b/fineract-war/build.gradle @@ -170,21 +170,11 @@ tasks.named('binaryDistTar') { ':fineract-provider:build', ':fineract-doc:doc', ':fineract-client:javadocJar', ':fineract-client:sourcesJar', ':fineract-avro-schemas:javadocJar', ':fineract-avro-schemas:sourcesJar') - - doLast { - file("${buildDir}/distributions/apache-fineract-binary-${version}.tar.gz") - .renameTo("${buildDir}/distributions/apache-fineract-${version}-binary.tar.gz") - } } tasks.named('srcDistTar') { description = 'Assembles the source distribution as a tar archive' outputs.cacheIf { true } - - doLast { - file("${buildDir}/distributions/apache-fineract-src-${version}.tar.gz") - .renameTo("${buildDir}/distributions/apache-fineract-${version}-src.tar.gz") - } } // Disable zip distributions as they're not needed
