You should definitely be using some kind of source control (at least locally… takes 5 minutes to setup)… and you may want to update your backup policy also.
Else, just keep the rope and tree handy as you’ll have this problem again and again… and again.
Edit: I mean, I assume you’ve looked on the disk itself to confirm it isn’t just removed from the SDK’s view.
Well its not like i worked for a year on same project without back up but the last one lose me a month of smoothing work… Well thnx for help . Still it could go for some bug list …
Maybe you’re lucky and its in the file history, I think it only works within projects, not for deleting whole projects. (Look in the help for file history, I can’t say off the top of my head where that option is either).
Here’s an interesting one for you. Just counted 8 deleted projects in my testing stuff. One was monkeyzone, which was still open, yet it showed as deleted with only the assets folder under the main folder when exploring the files.
Sure enough, closed the open monkeyzone project and now its gone…
I was working in the original that’s kept outside the jmonkey projects folder so I didn’t lose anything. That’s why it was still open when the jmonkeyzone project folder did get deleted. My bad.
Makes me wonder if keeping projects outside the jmonkey projects folder will prevent the deletion or if I just got lucky. Would hate to delete my frigging drive somehow randomly.
I use and love Bitbucket. Unlimited free repos for teams smaller than 5 people (I work alone at the moment), and you can use Mercurial instead of the gargoyle that is Git. You also get a wiki and simple issue tracker (which is handy even if you’re working alone).
Indeed. And the “throw away” projects count here, too. Though personally I tend to check those in also.
At home I use SVN. It’s easy to init a repo and especially for single person development it’s super easy. Any technical “knock” against subversion is always related to running remote or in teams (and even then the arguments tend to depend on the team). It’s also great at storing binaries (which git really sucks at).
Only reason I went with BitBucket was the “cloud” aspect of it, plus I use a Git system at my work. So trying to bolster my Git-fu in the same process. Otherwise Subversion is suuuuuper easy to use.
Same. The stuff I want to throw away today I might want to reference later.
I started using SVN. The trouble I had was merging nightmares, although I never took the time to properly learn it so that was probably purely my own fault. I really like Mercurial because it’s trivial to develop on both my laptop and desktop without having to merge, merges are generally painless and fully automatic when I do screw up and need to merge, and I can develop remotely without an internet connection and still have full access to my repo. There’s something marvelous about developing code on an airplane at 30,000 feet and still being able to keep a proper commit log. Plus, if you’re not using a cloud service like Bitbucket you don’t need to have a “central” repo - you can just push/pull between your two machines. I’m not fond of Git because the interface feels cobbled together. Mercurial has a very clean, simple, and elegant interface by comparison. Not sure how Mercurial handles binaries though - I wouldn’t be surprised if SVN still had the upper hand there.
Note: Usually this behavior should be inherent from netbeans, however I’ve also noted that regular files don’t get deleted when you click delete.
Not sure there is an easy way to recover anything, but some people want commits more often than once a day (say like any sub-feature).
Personally, I only commit once a week or so, when I’ve collected a big feature. Not that it would be good, but I’m not savagely deleting projects.