Build fails on blt vm:nuke if nuked previously

[mirsoftacquia]

My system information:

Operating system type: macOS
Operating system version: 10.12.3
BLT version: 8.6.15

How to reproduce:

1. Create a new project from the scratch, follow these instructions up to point 4: http://blt.readthedocs.io/en/8.x/readme/creating-new-project/
2. Destroy vm using blt vm:nuke
3. Initialize vm again using blt vm
4. Setup local environment again using blt local:setup
5. Destroy vm again using blt vm:nuke

Result:

Build failed. Output of the last blt vm:nuke command:

 blt > vm:nuke:

 This will destroy your VM, and delete all associated configuration. Continue? [y] :  y
     blted: Are you sure you want to destroy the 'blted' VM? [y/N] y
 ==> blted: Forcing shutdown of VM...
 ==> blted: Destroying VM and associated drives...
 ==> blted: Pruning invalid NFS exports. Administrator privileges will be required...
 Password:
 ==> blted: [vagrant-hostsupdater] Removing hosts

 BUILD FAILED/Users/wonttellyou/blted/./vendor/acquia/blt/phing/tasks/vm.xml:135:8: /Users/wonttellyou/blted/./vendor/acquia/blt/phing/tasks/vm.xml:140:159: Could not find file /Users/wonttellyou/blted/vendor/acquia/blt/template/drush/site-aliases/aliases.drushrc.php to copy.
 ; 23.5764 seconds

It happens because in vm.xml, the file aliases.drushrc.php was moved away from ${blt.root}/template/drush/site-aliases (typically this is in vendor folder) during the first blt vm:nuke command. Thus, the file is not present on second run of blt vm:nuke anymore. I think, the file aliases.drushrc.php should correctly be copied instead of being moved.