v1.0.0 Setup initial project

This page describes how a project should be setup using v1.0.0 release (or custom build from branch) in order to get all the functionality working properly.

TOC

• creating a new project
• reporting issues
• contributing

Create a new Project

Common

In 1.0.0 you need to take the following steps to create a new project and configure it properly:

• download the latest alpha release from Github releases section
• always install the zip file, don't extract it (Note for Mac OS X users: you need to download the entire zip file, not a several jars, [https://discussions.apple.com/thread/1483114](see Apple discussion forum))
• after the plugin is installed, restart the IDE

Now, please follow the steps according to your IDE:

IntelliJ IDEA

• create a new project by going to Create New Project | Go and follow the setup steps

Other IDEs

• create a new blank project and you'll be prompted to setup a GO SDK for it

Once you've created the project according to your IDE, please follow the steps below

• after your project has been created, you can then add your GOPATH packages to it so that you can use all the plugin features
• to do, go to File | Settings | Languages & Frameworks | Go Libraries. Here you have a few options to choose from, but the recommended (and most tested one at the moment) is to create a new entry under Global Libraries that points to your GOPATH directory (see the example bellow).
• if you've followed the steps correctly, then "everything" should work for you

One concrete example would be (under Linux, paths may vary on other OSes):

• GOROOT (aka sdk home) /usr/local/go
• GOPATH (the path in Go Libraries | Global Libraries) /home/florin/golang/
• project home /home/florin/golang/src/github.com/dlsniper/misc

For set SDK in Linux see this link http://stackoverflow.com/a/20533130/3380763

Reporting issues

"everything" means that everything that's supposed to work, will work, we are aware of some issues, please see our issue tracker before reporting anything.

Contributing

We also gladly accept contributions, be it in form of well explained and repeatable tests, code snippets that can reproduce the issue you are having or PRs to fix things or add missing functionality. Please see our contributing documentation to get you started.