Better support for GOPATH like projects.

[mtoader]

A local go module should be handled like an external go repository by using the GOPATH env variable appropriately.

[mtoader]

Issue #119 is tracking inspections necessary to allow a module to have a GOPATH compatible structure.

[mtoader]

#120 is tracking go build / install support for go modules.

[mtoader]

#121 is tracking cleanups on how the import paths vs package names are handled.

[AlexLuya]

If testing can be done as:right click --> pick "run as go test",a lot of time to swithing between command line and InteillJ will be saved.

[mtoader]

#122 to track easy go test command wrapping and handling.

[mtoader]

@AlexLuya can you point me to a small project (that is compatible an external go source code repository) that has tests so i can play a little ?

[AlexLuya]

Do you need a project with test?Try this one:
https://github.com/hoisie/web
Or You can publish a testing version(can be intalled in IntelliJ),I will test it.

[AlexLuya]

What is the priority for this feature in your todo list?I think it should be highest.Currently,I will do coding in GoIDE,then switch to command line to compile and copy for testing,waste a lot of time.

[mtoader]

This is the last feature that i want to build before the next release. While doing that if i hear about a show stopper bug i try to fix it.

Remember that this is only a tracking issue (meaning that no work is being directly on this). The work is done in the referenced tickets (that you should watch if you are impatient :)). The referenced tickets are in the comments of this issue but i'll refer them once again for your convenience here: #122, #121, #120, #119.

You should be happy to know that i started working on a runner for go test that should behave the same as run junit test is behaving for java code. It's not done yet but it's getting there. Also remember that i do this in my spare time (which is limited atm).

Mihai

[AlexLuya]

I know,thanks very much

[AlexLuya]

Owesome,test runner worked,but these is small problem,slow and keep getting warning:warning: building out-of-date packages:....installing these packages with 'go test -i mgd' will speed future tests.I googling and found this issue has been reported and fixed here:http://code.google.com/p/go/issues/detail?id=3023.Any special settings must be done?Or do I miss something?

[mtoader]

I think you need to run the test with -i flag set first. I'll add a setting in the test runner for this. In meantime you might as well just copy the command line of the test, add a -i flag and run it inside the console. I think the next runs will behave properly after that.

[netvl]

I guess I'll write here.
Currently it looks like that the plugin completely replaces GOPATH variable when running test configuration. However, I think it would be more logical if the plugin would add module directory to the end of GOPATH, so the paths that came from the system would not be affected.
Because of this, for example, I am currently unable to launch tests from inside Idea, because there are some libraries inside my system-wide GOPATH which my project uses, so when GOPATH become replaced, the project stops compiling.

[mtoader]

I see. This makes sense.

[dlsniper]

This can be closed now I guess.