Add re-usable Gradle task postBuild

[ghubstan]

Several new bisq-* repos are going to be pulled out of the large, multi-project bisq repo.

They must follow the parent repo's convention of copying startup scripts and jar lib directories into their respective repos' root directories. This repo's first shared script is task postBuild with description: "Makes distribution's start script runnable from project root directory."

Usage is described in the repo's README.md.

Based on main.

[ripcurlx]

As I'm no big gradle expert -> @alvasw Could you please review this PR? Thanks!

[ghubstan]

@alvasw @ripcurlx This bisq-pricenode branch uses the postBuild gradle task in this PR.
https://github.com/ghubstan/bisq-pricenode/tree/adjust-build-files-n-scripts

See https://github.com/ghubstan/bisq-pricenode/blob/adjust-build-files-n-scripts/build.gradle
https://github.com/ghubstan/bisq-pricenode/blob/adjust-build-files-n-scripts/.gitmodules

[ghubstan]

@alvasw @ripcurlx I need to anticipate a couple of questions from either of you about this PR.

1. Why isn't this task defined in the gitmodule bisq, to avoid creating a whole new repo just for gradle tasks?

   I am using the latest gradle version in the new bisq-* repos, and I'm not supposed to be optimizing the big bisq v1 repo's build. I'm taking that requirement a bit further by not upgrading bisq's gradle version. (And I'm not spending any time to make sure any of the gradle tasks I put in this repo are backward compatible to v 7.3.3.)

   Optimizing bisq v1's build and upgrading its gradle version will easier to do after many of its subprojects are moved into new bisq-* repos. When the bisq v1 repo's gradle version is upgraded to match the new bisq-* repos' gradle version, I can move everything in bisq-gradle/task back into bisq, adjust the new bisq-* repo builds, and delete this bisq-gradle repository.

2. Why didn't I put these extra gradle tasks in a plugin?

   I tried that first. I put the postBuild task in a precompiled script plugin, made it a git submodule dependency in bisq-pricenode's build, but could not reference the plugin's id in bisq-pricenode's build. I gave up, and opted for a folder with this first script.

[alvasw]

Hi @ghubstan!
It looks good so far!

Why isn't this task defined in the gitmodule bisq, to avoid creating a whole new repo just for gradle tasks?
I am using the latest gradle version in the new bisq-* repos, and I'm not supposed to be optimizing the big bisq v1 repo's build. I'm taking that requirement a bit further by not upgrading bisq's gradle version. (And I'm not spending any time to make sure any of the gradle tasks I put in this repo are backward compatible to v 7.3.3.)
Optimizing bisq v1's build and upgrading its gradle version will easier to do after many of its subprojects are moved into new bisq-* repos. When the bisq v1 repo's gradle version is upgraded to match the new bisq-* repos' gradle version, I can move everything in bisq-gradle/task back into bisq, adjust the new bisq-* repo builds, and delete this bisq-gradle repository.

Makes sense to me.

Why didn't I put these extra gradle tasks in a plugin?
I tried that first. I put the postBuild task in a precompiled script plugin, made it a git submodule dependency in bisq-pricenode's build, but could not reference the plugin's id in bisq-pricenode's build. I gave up, and opted for a folder with this first script.

Did you push your attempt where you tried to use a precompiled script plugin somewhere? I can take a look at it if you want to. I think that it's cleaner. In Bisq 2, we're using and referencing precompiled script plugins.
But this should work as well!

[ghubstan]

Did you push your attempt where you tried to use a precompiled script plugin somewhere? I can take a look at it if you want to. I think that it's cleaner. In Bisq 2, we're using and referencing precompiled script plugins.
But this should work as well!

I deleted it, and just pushed it back & made you a collaborator: https://github.com/ghubstan/bisq-post-assemble-plugin

What I couldn't get to work was its use in another repo, after making bisq-post-assemble-plugin a git submodule in the user project:

plugins {
    id 'application'
    id 'bisq.post-assemble'
}

The script itself is a mess (no matter, not the problem). This PR's postBuild task you said "should work as well" is better script.
But if you figure out what I did wrong, I'll move this to a new script plugin after some loose ends are taken care of (waiting for other bisq-* repo reviews).

[alvasw]

I fixed it. Take a look at [1] for the changes in the plugin and at [2] on how to use it in other repositories.

[1] https://github.com/ghubstan/bisq-post-assemble-plugin/tree/convert_to_standalone_plugin
[2] https://github.com/alvasw/bisq-pricenode/tree/adjust-build-files-n-scripts

[ghubstan]

Closed, replaced by PR #2