Community
Participate
Working Groups
heres the idea, sometimes i have a class file(s) in a java project that i no longer need but at the same time i don't want to delete it as i might need the code for reference or something later, so what you do is right click it and send it to trash, now it no longer interfers with your project no references can point to it and its out of the way. later if need be you can restore it or view it, what do you ppl think? p.s. i know you can create another package but this is fidly and time consuming something quick and fast like this is what i need!
*** Bug 117191 has been marked as a duplicate of this bug. ***
*** Bug 117194 has been marked as a duplicate of this bug. ***
*** Bug 117196 has been marked as a duplicate of this bug. ***
You can simply exclude it from your buildpath, so it doesn't get in the way; then you can later restore it.
was thinking more on the lines of a quick archiving thing, also if the file still remains in the same package adds to clutter and other classes can still link to it in the eclipse editor and can get a little cumbersome, especially if you wanna move lots of files
When excluded, a file no longer appears in the same package. Also the file is not physically moving, thus it will not appear as a true change for CVS. If the file is moved elsewhere, it could intefere with source control. Is this what you anticipated ?
(In reply to comment #6) yes, basically you are deleting the file, but keeping a copy archieved somewhere else, just in case you might need it again.
maybe even just keeping it locally, while deleting it off the server.
