Github user geomacy commented on the pull request:
https://github.com/apache/brooklyn-client/pull/6#issuecomment-196321059
The way I have it at the moment is to try to make the package
simultaneously be
1. A regular Go module that expects to be built within the usual GOPATH
structure, and
2. A regular Maven module that can be cloned and built at any arbitrary
location
to do this, I have set up the Maven build to ignore any pre-existing GOPATH
and to redefine GOPATH itself, pointing at the target directory. That way you
can do a Maven build without worrying about what's on your GOPATH or whether
you even have one (for developers who don't care about Go - of course you do
still need Go itself installed, but you don't need to think about setting up a
Go workspace etc.)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
