search

quan-xie / goclipse

Automatically exported from code.google.com/p/goclipse
0 stars 0 forks source link

Import existing project of type go fails to build on the fly #97

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create a new go project with a source file (test working)
2. Remove project from eclipse (do not delete sources)
3. Import deleted project into eclipse. Source file no longer is built on the 
fly - type in an error and no marker appears.

What is the expected output? What do you see instead?
The project to behave normally

What version of the product are you using? On what operating system?
0.7.1.v385

Original issue reported on code.google.com by notzi...@gmail.com on 18 Apr 2012 at 10:22

GoogleCodeExporter commented 9 years ago 
I get the same problem.  This problem also continues to occur even if I use the 
"Convert to Go Project" option.  When using that, it does show the GOROOT 
folder in the tree as expected, but it still fails to do the auto-building.

My current workaround is to create a new project and then manually copy the old 
project contents into the new project.  I would like it to just work straight 
away with an import.

It seems to also work to create a new Go project but tell it to use existing 
source, but that causes it to leave the existing source where it is instead of 
importing it into the workspace folder.  I want the files in that workspace, so 
I can't use this method myself.  If you like your project files to be scattered 
around in various locations outside of your workspace, you may prefer this 
method.

Original comment by dustyisa...@gmail.com on 2 May 2012 at 5:11