Skip to content

FINERACT-2637: simpler build commands#5973

Open
meonkeys wants to merge 1 commit into
apache:developfrom
meonkeys:simple-build
Open

FINERACT-2637: simpler build commands#5973
meonkeys wants to merge 1 commit into
apache:developfrom
meonkeys:simple-build

Conversation

@meonkeys

Copy link
Copy Markdown
Contributor

Description

WIP / proposal for simpler build commands

I'd love to simplify our build commands if possible. I'm hoping we can safely make use of the Gradle daemon to save on Java startup times and we can let Gradle handle caching while using fewer explicit ("-x") exclusions. If so, the commands would be easier to read, maintain, and reproduce apart from GitHub Actions (e.g. during local dev/test).

Guidance from Ádám Sághy:

our gradle task dependencies should be rather reviewed first why any of the excluded tasks been triggered (hence depended) for the target task

FINERACT-2637

Checklist

Please make sure these boxes are checked before submitting your pull request - thanks!

  • Write the commit message as per our guidelines
  • Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.
  • Create/update unit or integration tests for verifying the changes made.
  • Follow our coding conventions.
  • Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes
  • This PR must not be a "code dump". Large changes can be made in a branch, with assistance. Ask for help on the developer mailing list.

Your assigned reviewer(s) will follow our guidelines for code reviews.

WIP / proposal for simpler build commands

I'd love to simplify our build commands if possible. I'm hoping we can
safely make use of the Gradle daemon to save on Java startup times and
we can let Gradle handle caching while using fewer explicit ("-x")
exclusions. If so, the commands would be easier to read, maintain, and
reproduce apart from GitHub Actions (e.g. during local dev/test).

Guidance from Ádám Sághy:

> our gradle task dependencies should be rather reviewed first why any
> of the excluded tasks been triggered (hence depended) for the target
> task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant