gerrit/.buckconfig
David Ostrovsky 358a4582fd Move gerrit.war from api_{install,deploy} to war_{install,deploy}
I22c8d3339 added unconditionally installation of gerrit.war to API install
process.  Because it depends on '//:release' target all core plugins,
documentation and optimized permutations of all supported GWT client
agents must be built to update a new version of plugin API.

In some cases it cannot be built at all, i.e. if Gerrit tree was cloned
non-recursively, and core plugins are not available.

Very repetitive tasks in development process like building new version of
plugin API that other plugins depend on should be very easy and fast doable.

Decouple installation and deployment of gerrit.war in its own targets:

  $ buck build war_{install,deploy}

Change-Id: I7fce3b126621580dde43104aa811d704cf6e8997
2014-05-20 06:41:08 +00:00

25 lines
464 B
Plaintext

[alias]
api = //:api
api_deploy = //tools/maven:api_deploy
api_install = //tools/maven:api_install
war_deploy = //tools/maven:war_deploy
war_install = //tools/maven:war_install
chrome = //:chrome
docs = //Documentation:html
gerrit = //:gerrit
release = //:release
withdocs = //:withdocs
[buildfile]
includes = //tools/default.defs
[java]
src_roots = java, resources
[project]
ignore = .git
[cache]
mode = dir
dir = buck-out/cache