I've recently had to move my code from one pc to another (oddly enough a windows terminal to a linux desktop).
fortunately (at least I thought) I had regularly exported the code using the export function in eclipse, and saved the copy onto a USB key.
So I simply 'imported' the code I had on the key into a new workspace on my new desktop. Things seemed happy and jolly. Obviously I needed to fix a few issues with paths and locations of libraries I had used, and make minor updates to some ant files. Nothing to major.
After having done all this I expected the various build path errors that I was getting would be resolved. Unfortunately not.
After much messing around with the various build paths of the files that where causing me grief I decided I would try to simple copy and paste the code in the files into a new class.
So I renamed the original class (appending _old to the name using eclipses refactor process). I created a new java class file, then copy / pasted the code frome the _old file to the new one, obviously I altered the name of the class and the constructor on the way.
The new files throw out no build path error, or anything else that concerns me (I still have some unused imports, but I will tidy these up when my development has finished for these libraries)
My question is, is this a problem with Eclipse (I'm still using indigo as I found juno very slow?), and if so, how can I troubleshoot to create a sensible bug report?
Or is it something else that I did wrong in my export / import ?
Thanks in advance for any comments.
David.