Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace gradle in standard build process #30

Open
terabyte opened this issue Mar 16, 2018 · 1 comment
Open

Replace gradle in standard build process #30

terabyte opened this issue Mar 16, 2018 · 1 comment
Labels
discussion Potential change that requires discussion enhancement help wanted standard java build process relating to the standard java build process

Comments

@terabyte
Copy link
Member

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.

@terabyte terabyte added enhancement help wanted discussion Potential change that requires discussion standard java build process relating to the standard java build process labels Mar 16, 2018
@terabyte
Copy link
Member Author

Alternative idea: replace with bazel or something else?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Potential change that requires discussion enhancement help wanted standard java build process relating to the standard java build process
Projects
None yet
Development

No branches or pull requests

1 participant