mirrors/jgit - jgit - source @ dussan.org

Tree: a2d3c376a6

Auteur	SHA1	Bericht	Datum
David Ostrovsky	2d0fc6124d	Buck: Simplify root build file Remove all proxy rules, that were introduced to allow to build Gerrit with hijacked JGit cell. New approach suggested in: [1], that emulates real JGit project structure in its own cell, makes them unnecessary. Add :all rule, that build all artifacts and packages them in zip file. Add shell binary :jgit_bin rule, that allows to execute JGit binary from with buck run command, e.g.: $ buck run jgit_bin status $ buck run jgit_bin -- --version * [1] https://gerrit-review.googlesource.com/74859 Change-Id: Idf9ecb783cbd2b9984d4118047968f1f5204d642 Signed-off-by: David Ostrovsky <david@ostrovsky.org>	8 jaren geleden
Saša Živkov	dcfcbfd8bf	Add Buck build aliases Change-Id: I6aa2a8f094d36ef04dd12c81dfba8328e4a3bee9	8 jaren geleden
Shawn Pearce	2f8d787b5f	buck: run tests Compile each test in its own java_test() target so they can run in parallel, reducing total time spent testing on large machines. $ buck test --all [-] PROCESSING BUCK FILES...FINISHED 0.3s [100%] [-] BUILDING...FINISHED 2.9s [100%] (351/383 JOBS, 351 UPDATED, 0.0% CACHE MISS) [-] TESTING...FINISHED 98.1s (3360 PASS/15 SKIP/0 FAIL) Change-Id: I8d6541268315089299f933ed23d785b1b3431133	8 jaren geleden
David Ostrovsky	13502fef8f	Implement Buck driven build Today there are plenty of modern build tool systems available in the wild (in no particular order): * http://bazel.io * https://pantsbuild.github.io * http://shakebuild.com * https://ninja-build.org * https://buckbuild.com The attributes, that all these build tools have in common, are: * reliable * correct * very fast * reproducible It must not always be the other build tool, this project is currently using. Or, quoting Gerrit Code Review maintainer here: "Friends, don't let friends use <the other build tool system>!" This change is non-complete implementation of JGit build in Buck, needed by Gerrit Code Review to replace its dependency with standlone JGit cell. This is very useful when a developer is working on both projects and is trying to integrate changes made in JGit in Gerrit. The supported workflow is: $ cd jgit $ emacs <hack> $ cd ../gerrit $ buck build --config repositories.jgit=../jgit gerrit With --config repositories.jgit=../jgit jgit cell is routed through JGit development tree. To build jgit, issue: $ buck build //:jgit [-] PROCESSING BUCK FILES...FINISHED 0,0s Yes, you can't measure no-op build time, given that Buck daemon is used. Change-Id: I301a71b19fba35a5093d8cc64d4ba970c2877a44 Signed-off-by: David Ostrovsky <david@ostrovsky.org>	8 jaren geleden

4 Commits (a2d3c376a682b540ecd87fe3ff2ffebc1766f938)