Handle the scenario: run external build, click 'delete database' in UI, see what happens; possible outcomes:
- database is loaded again after build is finished
- deletion fails (at the time when JSP creates a locks a file) - any error message in UI? ignore the problem?
- closing instrumentation session fails (at the time when file is being deleted from IDE - file is locked - the JPS will try to open it and append new instrumentation session); ignore the problem as user actually wanted to delete database? add some notification popup about this?
Improved error handling in case when db is locked: