Expand the dependencies section in the buck documentation
Mention that it is currently only possible to download dependencies
over HTTP from the source sites, and `http_proxy` should be set when
running behind an HTTP proxy.
Also make sure we consistently add two blank lines before headlines,
and one blank line after, in the rest of the document.
Change-Id: I4c85fe5f47a9d78b6c07eee18f2173980ce5c25f
diff --git a/Documentation/dev-buck.txt b/Documentation/dev-buck.txt
index 5f10e47..460fa71 100644
--- a/Documentation/dev-buck.txt
+++ b/Documentation/dev-buck.txt
@@ -55,6 +55,7 @@
Expand the `gerrit` project, right-click on the `buck-out` folder, select
'Properties', and then under 'Attributes' check 'Derived'.
+
Refreshing the Eclipse Project
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -102,6 +103,7 @@
buck-out/gen/{extension,plugin}-api.jar
----
+
Running Unit Tests
------------------
@@ -118,13 +120,12 @@
----
-
Dependencies
------------
Dependency JARs are normally downloaded automatically, but Buck can inspect
its graph and download any missing JAR files. This is useful to enable
-builds to run without network access.
+subsequent builds to run without network access.
Force a download of dependency JARs by building the `download` target:
@@ -132,6 +133,19 @@
buck build download
----
+Currently there is no way to download dependencies other than over an HTTP
+connection from the source sites (Maven Central and the Gerrit storage
+bucket). It is not yet possible to use, for example, a corporate Nexus
+proxy.
+
+When downloading from behind a proxy (which is common in some corporate
+environments), it might be necessary to explicitly specify the proxy that
+is then used by `curl`:
+
+----
+ export http_proxy=http://<proxy_user_id>:<proxy_password>@<proxy_server>:<proxy_port>
+----
+
Build Process Switch Exit Criteria
----------------------------------
