brooklyn-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [27/50] [abbrv] brooklyn-client git commit: More notes on build process.
Date Tue, 08 Mar 2016 13:20:00 GMT
More notes on build process.


Branch: refs/heads/master
Commit: 80b0cdf4ee8821f8344b265e7ec3b38128db65ad
Parents: 924fb59
Author: Geoff Macartney <>
Authored: Wed Feb 24 21:04:38 2016 +0000
Committer: Geoff Macartney <>
Committed: Wed Feb 24 21:04:38 2016 +0000

---------------------------------------------------------------------- | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/ b/
index 4551dfb..e8b6077 100644
--- a/
+++ b/
@@ -78,7 +78,6 @@ where the username and password need only be supplied if Brooklyn requires
     $ sh  http://your-brooklyn-host:8081 myuser mypassword
-    exit 0
 Note, the tests are not yet comprehensive, and contributions are welcome.
@@ -95,6 +94,13 @@ Invoke the build script via Maven with one of
   - ```mvn -Dtarget=native clean install```                     build for the current platform
   - ```mvn -Dtarget=cross -Dos=OS -Darch=ARCH clean install```  build for platform with operating
system OS and architecture ARCH
+*NOTE* This does *not* build the code into your usual GOPATH. To allow the project to be
checked out along with the 
+other Brooklyn submodules and built using Maven, without any special treatment to install
it into a separate GOPATH
+location, the Maven build makes no assumption about the location of the project root directory.
Instead, the Maven
+`target` directory is used as the GOPATH, and a soft link is created as `target/src/`
+the code in the root directory. If godep is already installed in the PATH, it is used, otherwise
Go is used to fetch
+godep and install it.  The CLI dependencies need not be fetched as they are used from the
Godeps directory by godep. 
 This builds the requested binaries into the "target" directory, each in its own subdirectory
with a name that includes 
 the platform/architecture details, e.g. bin/linux.386/br.  The build installs a maven artifact
to the maven repository,
 consisting of a zip file containing all the binaries.  This artifact can be referenced in
a POM as

View raw message