Examples of a GoLand-compatible project structure?

<p>I have tried probably 100 different ways to setup my project in a way that GoLand will recognize all of my external dependencies and auto-generated modules from protobuf but I can&#39;t seem to figure it out. Everything I try GoLand complains about not being able to resolve dependencies under src/vendor/ or vendor/.</p> <p>As an example demonstrating my problem, <a href="https://github.com/minaandrawos/Go-Protobuf-Examples" rel="nofollow">https://github.com/minaandrawos/Go-Protobuf-Examples</a> uses a structure similar to mine and is filled with GoLand dependency errors.</p> <p>Does anyone have an example of a project structure that is compatible with GoLand?</p> <hr/>**评论：**<br/><br/>dlsniper: <pre><p>Make sure your project is in GOPATH, as described here, <a href="https://golang.org/doc/code.html#Workspaces" rel="nofollow">https://golang.org/doc/code.html#Workspaces</a>, that the IDE GOPATH setting is pointing to the same GOPATH (via Settings | Go | GOPATH), and that should be it.</p> <p>If this doesn&#39;t work, open an issue on our tracker, <a href="https://youtrack.jetbrains.com/issues/Go" rel="nofollow">https://youtrack.jetbrains.com/issues/Go</a>, and provide the IDE logs via Help | Compress Logs and Show in... and attach the zip file created.</p> <p>Thank you.</p></pre>dazzford: <pre><p>Why keep fighting with goland? There are plenty of other editors out there with great support which don&#39;t break.</p></pre>dlsniper: <pre><p>Because if it breaks in our editor at least we&#39;ll do everything we can to offer a solution to fix the problem. And because if it breaks in our editor, it will break in those alternatives as well.</p></pre>dazzford: <pre><blockquote> <p>Because if it breaks in our editor at least we&#39;ll do everything we can to offer a solution to fix the problem. And because if it breaks in our editor, it will break in those alternatives as well.</p> </blockquote> <p>Meh; I&#39;m guessing you are from jetbrains.</p> <p>I&#39;ve heard more people have issues with Goland than vim or vscode. Not sure why people decided to downvote my comment; I&#39;m guessing it was you and your co-workers. </p> <p>Not sure thats a good way to manage your brand.</p></pre>Emacs24: <pre><p>Because it is clear something is wrong with the OP setup as I have never had such a problem and never heard about it from others.</p> <p>For me it always was just <code>goland $GOPATH/src/&lt;path to package&gt;</code></p></pre>