Skip to content

Replace gradle in standard build process #30

@terabyte

Description

@terabyte

What's the deal with Gradle?

Pros:

  • it "just works"
  • it can run our unit tests for us
  • it reliably builds jars from java source code
  • most devs understand how it works and thus the build.gradle is transparent

Cons:

  • slow (have to disable gradle daemon for correctness, etc)
  • needlessly complex
  • large binary dependency

We've tried to replace gradle with a PoC shell script to invoke javac on the packages, it was surprisingly difficult, and that isn't even taking into account the shenanigans that would be necessary to run tests.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions