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
|
|
|
maven_jar(
|
|
|
|
|
name = 'jsch',
|
|
|
|
|
bin_sha1 = '658b682d5c817b27ae795637dfec047c63d29935',
|
|
|
|
|
src_sha1 = '791359d94d6edcace686a56d0727ee093a2f7c33',
|
|
|
|
|
group = 'com.jcraft',
|
|
|
|
|
artifact = 'jsch',
|
|
|
|
|
version = '0.1.53',
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
maven_jar(
|
|
|
|
|
name = 'javaewah',
|
|
|
|
|
bin_sha1 = '94ad16d728b374d65bd897625f3fbb3da223a2b6',
|
|
|
|
|
src_sha1 = 'ca2745e91c6a51f8e6809d1579bda36ad83f1f58',
|
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
|
|
|
group = 'com.googlecode.javaewah',
|
|
|
|
|
artifact = 'JavaEWAH',
|
|
|
|
|
version = '1.1.6',
|
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
|
|
|
)
|
|
|
|
|
|
|
|
|
|
maven_jar(
|
|
|
|
|
name = 'httpcomponents',
|
|
|
|
|
bin_sha1 = '4c47155e3e6c9a41a28db36680b828ced53b8af4',
|
|
|
|
|
src_sha1 = 'af4d76be0c46ee26b0d9d1d4a34d244a633cac84',
|
|
|
|
|
group = 'org.apache.httpcomponents',
|
|
|
|
|
artifact = 'httpclient',
|
|
|
|
|
version = '4.3.6',
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
maven_jar(
|
|
|
|
|
name = 'httpcore',
|
|
|
|
|
bin_sha1 = 'f91b7a4aadc5cf486df6e4634748d7dd7a73f06d',
|
|
|
|
|
src_sha1 = '1b0aa62a6a91e9fa00c16f0a4a2c874804ed3b1e',
|
|
|
|
|
group = 'org.apache.httpcomponents',
|
|
|
|
|
artifact = 'httpcore',
|
|
|
|
|
version = '4.3.3',
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
maven_jar(
|
|
|
|
|
name = 'commons-logging',
|
|
|
|
|
bin_sha1 = 'f6f66e966c70a83ffbdb6f17a0919eaf7c8aca7f',
|
|
|
|
|
src_sha1 = '28bb0405fddaf04f15058fbfbe01fe2780d7d3b6',
|
|
|
|
|
group = 'commons-logging',
|
|
|
|
|
artifact = 'commons-logging',
|
|
|
|
|
version = '1.1.3',
|
|
|
|
|
)
|
|
|
|
|
|
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
|
|
|
maven_jar(
|
|
|
|
|
name = 'slf4j-api',
|
|
|
|
|
bin_sha1 = '0081d61b7f33ebeab314e07de0cc596f8e858d97',
|
|
|
|
|
src_sha1 = '58d38f68d4a867d4552ae27960bb348d7eaa1297',
|
|
|
|
|
group = 'org.slf4j',
|
|
|
|
|
artifact = 'slf4j-api',
|
|
|
|
|
version = '1.7.2',
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
maven_jar(
|
|
|
|
|
name = 'slf4j-simple',
|
|
|
|
|
bin_sha1 = '760055906d7353ba4f7ce1b8908bc6b2e91f39fa',
|
|
|
|
|
src_sha1 = '09474919128b3a7fcf21a5f9c907f5251f234544',
|
|
|
|
|
group = 'org.slf4j',
|
|
|
|
|
artifact = 'slf4j-simple',
|
|
|
|
|
version = '1.7.2',
|
|
|
|
|
)
|
|
|
|
|
|
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
|
|
|
maven_jar(
|
|
|
|
|
name = 'servlet-api',
|
|
|
|
|
bin_sha1 = '3cd63d075497751784b2fa84be59432f4905bf7c',
|
|
|
|
|
src_sha1 = 'ab3976d4574c48d22dc1abf6a9e8bd0fdf928223',
|
|
|
|
|
group = 'javax.servlet',
|
|
|
|
|
artifact = 'javax.servlet-api',
|
|
|
|
|
version = '3.1.0',
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
maven_jar(
|
|
|
|
|
name = 'commons-compress',
|
|
|
|
|
bin_sha1 = 'c7d9b580aff9e9f1998361f16578e63e5c064699',
|
|
|
|
|
src_sha1 = '396b81bdfd0fb617178e1707ef64832215307c78',
|
|
|
|
|
group = 'org.apache.commons',
|
|
|
|
|
artifact = 'commons-compress',
|
|
|
|
|
version = '1.6',
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
maven_jar(
|
|
|
|
|
name = 'tukaani-xz',
|
|
|
|
|
bin_sha1 = '66db21c8484120cb6a51b5b3ea47b6f383942bec',
|
|
|
|
|
src_sha1 = '6396220725701d767c553902c41120d7bf38e9f5',
|
|
|
|
|
group = 'org.tukaani',
|
|
|
|
|
artifact = 'xz',
|
|
|
|
|
version = '1.3',
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
maven_jar(
|
|
|
|
|
name = 'args4j',
|
|
|
|
|
bin_sha1 = '139441471327b9cc6d56436cb2a31e60eb6ed2ba',
|
|
|
|
|
src_sha1 = '22631b78cc8f60a6918557e8cbdb33e90f63a77f',
|
|
|
|
|
group = 'args4j',
|
|
|
|
|
artifact = 'args4j',
|
|
|
|
|
version = '2.0.15',
|
|
|
|
|
)
|
|
|
|
|
|
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
|
|
|
maven_jar(
|
|
|
|
|
name = 'junit',
|
|
|
|
|
bin_sha1 = '4e031bb61df09069aeb2bffb4019e7a5034a4ee0',
|
|
|
|
|
src_sha1 = '28e0ad201304e4a4abf999ca0570b7cffc352c3c',
|
|
|
|
|
group = 'junit',
|
|
|
|
|
artifact = 'junit',
|
|
|
|
|
version = '4.11',
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
maven_jar(
|
|
|
|
|
name = 'hamcrest-library',
|
|
|
|
|
bin_sha1 = '4785a3c21320980282f9f33d0d1264a69040538f',
|
|
|
|
|
src_sha1 = '047a7ee46628ab7133129cd7cef1e92657bc275e',
|
|
|
|
|
group = 'org.hamcrest',
|
|
|
|
|
artifact = 'hamcrest-library',
|
|
|
|
|
version = '1.3',
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
maven_jar(
|
|
|
|
|
name = 'hamcrest-core',
|
|
|
|
|
bin_sha1 = '42a25dc3219429f0e5d060061f71acb49bf010a0',
|
|
|
|
|
src_sha1 = '1dc37250fbc78e23a65a67fbbaf71d2e9cbc3c0b',
|
|
|
|
|
group = 'org.hamcrest',
|
|
|
|
|
artifact = 'hamcrest-core',
|
|
|
|
|
version = '1.3',
|
|
|
|
|
)
|
|
|
|
|
|
|
|
|
|
maven_jar(
|
|
|
|
|
name = 'gson',
|
|
|
|
|
bin_sha1 = 'a60a5e993c98c864010053cb901b7eab25306568',
|
|
|
|
|
src_sha1 = 'a6dc5db8a12928e583bd3f23e72d3ab611ecd58f',
|
|
|
|
|
group = 'com.google.code.gson',
|
|
|
|
|
artifact = 'gson',
|
|
|
|
|
version = '2.2.4',
|
|
|
|
|
)
|
