2016-02-12 18:09:31 +02:00
|
|
|
[alias]
|
2016-02-14 12:36:25 +02:00
|
|
|
all = //:all
|
|
|
|
jgit = //org.eclipse.jgit:jgit
|
|
|
|
jgit-archive = //org.eclipse.jgit.archive:jgit-archive
|
2016-02-12 18:09:31 +02:00
|
|
|
jgit_bin = //:jgit_bin
|
2016-02-14 12:36:25 +02:00
|
|
|
jgit-lfs = //org.eclipse.jgit.lfs:jgit-lfs
|
|
|
|
jgit-lfs-server = //org.eclipse.jgit.lfs.server:jgit-lfs-server
|
|
|
|
jgit-servlet = //org.eclipse.jgit.http.server:jgit-servlet
|
2016-02-12 18:09:31 +02:00
|
|
|
|
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>
2015-12-04 09:27:57 +02:00
|
|
|
[buildfile]
|
|
|
|
includes = //tools/default.defs
|
|
|
|
|
|
|
|
[java]
|
2015-12-31 20:44:30 +02:00
|
|
|
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>
2015-12-04 09:27:57 +02:00
|
|
|
|
|
|
|
[project]
|
|
|
|
ignore = .git
|
|
|
|
|
|
|
|
[cache]
|
|
|
|
mode = dir
|
|
|
|
|
|
|
|
[download]
|
|
|
|
maven_repo = http://repo1.maven.org/maven2
|
|
|
|
in_build = true
|