jgit/.buckconfig

[alias]
  jgit = //:jgit
  jgit-servlet = //:jgit-servlet
  jgit-archive = //:jgit-archive
  jgit-lfs = //:jgit-lfs
  jgit-lfs-server = //:jgit-lfs-server
  jgit_bin = //:jgit_bin

[buildfile]
  includes = //tools/default.defs

[java]
  src_roots = src, resources, tst

[project]
  ignore = .git

[cache]
  mode = dir

[download]
  maven_repo = http://repo1.maven.org/maven2
  in_build = true
Add Buck build aliases Change-Id: I6aa2a8f094d36ef04dd12c81dfba8328e4a3bee9 9 years ago			`[alias]`
			`jgit = //:jgit`
			`jgit-servlet = //:jgit-servlet`
			`jgit-archive = //:jgit-archive`
			`jgit-lfs = //:jgit-lfs`
			`jgit-lfs-server = //:jgit-lfs-server`
			`jgit_bin = //:jgit_bin`

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> 9 years ago			`[buildfile]`
			`includes = //tools/default.defs`

			`[java]`
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 9 years ago			`src_roots = src, resources, tst`
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> 9 years ago
			`[project]`
			`ignore = .git`

			`[cache]`
			`mode = dir`

			`[download]`
			`maven_repo = http://repo1.maven.org/maven2`
			`in_build = true`