Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • B bjgf
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 127
    • Issues 127
    • List
    • Boards
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • BlueJ
  • bjgf
  • Issues
  • #12
Closed
Open
Issue created Sep 06, 2007 by Neil Brown@nccbMaintainer

[BLUEJ-12] compiling with no free space saves an empty file

Hello, due to third party applications I ran out of free disk space on the partition where my project was. Without noticing that, I was working on the project with one editor window opened and when I hit the Compile button a message popped saying it couldn't save the changes and when I clicked Ok, the editor window was empty. No undo, nothing... I checked the project folder and the .java file was 0Bytes sized. My luck was that I only changed one class, because I assume that if I changed more files, I'd lose them all.

This behavior needs to change, because it's not ok to abandon the contents of the class like this. The class was saved and compiled many times before this, so BlueJ saved an empty file over the old not-empty one. It should refuse to compile/save the files before having the free space and keep everything as before... or something like that.

Thanks.

---

A copy of the file is saved before overwriting (named ClassName.java#). This can be used for restoring contents.

Maybe that should be done automatically...


Issue metadata

  • Issue type: Bug
  • Priority: Low
  • Fix versions: 2.5.1
Assignee
Assign to
Time tracking