|
|
|
|
|
Re: where to report this bug in eclipse 4.9 [message #1798312 is a reply to message #1797941] |
Thu, 15 November 2018 08:17 |
Patrick Moran Messages: 141 Registered: March 2018 |
Senior Member |
|
|
I have seen this kind of thing from Eclipse very often. I have been working on one project for a rather long time, and I try to avoid getting everything messed up if I make one mistake by copying projects over and over again, so I get
Tomcat_1
Tomcat_2
Tomcat_n
Working on Tomcat_n I am likely to get some "borrowing" from an earlier version. Or, if I change to another project, e.g., Fishback_3, and I just run it to be reminded of how it works, Eclipse will run Tomcat_n unless I edit Fishbacck_3. It doesn't matter what I do, add a single letter and erase it is enough, then I save, and after that Eclipse lets go of Tomcat.
When I was just getting started this kind of thing drove me crazy.. Even worse, if I did something very wrong with Tomcat_n then all the Tomcat projects might be corrupted.
Because of this group suicide movement, I started making new Workspaces every time I got to something that was really worth saving even if it was just a milestone along the way. That way if I programmed in an infinite loop or whatever, I would only lose a few of the most recent trials, and they probably wouldn't be of any use anyway.
Eclipse keeps all sorts of stuff in invisible configuration files of some kind. I think that is where versions are getting lumped together. My stuff is particularly prone to trouble, I suspect, because I keep all the same blocks of code from version to version, plus or minus some change.
|
|
|
Powered by
FUDForum. Page generated in 0.05995 seconds