From a9796f4378b6959a130e0a79884d8e2f118ad0c2 Mon Sep 17 00:00:00 2001 From: Cedric Beust Date: Tue, 6 Dec 2016 14:52:59 -0800 Subject: [PATCH] Document proxies. --- documentation/index.html | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) diff --git a/documentation/index.html b/documentation/index.html index f705f59..8ef52e7 100644 --- a/documentation/index.html +++ b/documentation/index.html @@ -300,6 +300,12 @@ dependencies { <repo>http://jcenter.com</repo> <repo>http://example.com</repo> </defaultRepos> + <proxies> + <proxy> + <host>proxy-host.com</host> + <port>1234</port> + </proxy> + </proxies> </kobaltSettings>

Here is a list of the parameters you can configure: @@ -343,8 +349,12 @@ dependencies { ~/.kobalt/localMavenRepo Where Kobalt publishes artifacts when the task publishToLocalMaven is invoked. + + proxies + None + One or more proxies that Kobalt will use to download Maven dependencies. + -

Templates

Templates are invoked with the --init parameter and typically used when you are creating @@ -696,8 +706,15 @@ New versions found: Use this flag if Kobalt just notified you that a new version is available and you want to update. Another way of doing this is to edit kobalt/wrapper/kobalt-wrapper.properties manually. +

+ Note: If the --update parameter can't download Kobalt because your machine is + behind a proxy, you can specify that proxy as a system environment variable when launching the JVM + to run Kobalt: +

java -DhttpProxy=host:port -jar kobalt/wrapper/kobalt-wrapper.jar --update
+

-

Testing

+ +

Testing

Kobalt automatically detects how to run your tests based on the test dependencies that you declared: