What steps will reproduce the problem?
1. Create a pkg 'foo' with the standard layout proposed by goclipse (in
src/pkg)
2. Create a cmd 'bar' with the standard layout proposed by goclipse (in
src/cmd)
3. Try to debug 'bar' from the command line -- you can't because you have not
yet goinstalled 'foo'
4. goinstall 'foo' so it is in your standard set of packages
5. debug 'bar' using gdb
6. return to goclipse and make changes to 'foo'
7. run 'bar' from inside eclipse -- you end up with 'bar' linked against the
goinstalled version of 'foo' not the current version in eclipse
What is the expected output? What do you see instead?
Expected to always be linking any commands (src/cmd directory) with the
packages under development in the src/pkg directory.
What version of the product are you using? On what operating system?
goclipse 0.2.1 (via the update site) on Mac OS X, Snow Leopard
Please provide any additional information below.
This is not really a *bug* in the strictest sense, but it does provide a nasty
surprise if you mix command line work with development in goclipse.
Original issue reported on code.google.com by ians...@gmail.com on 24 Oct 2011 at 2:57
Original issue reported on code.google.com by
ians...@gmail.comon 24 Oct 2011 at 2:57