Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

FileTools has good copy function #13

Open
calvertdw opened this issue Mar 28, 2018 · 0 comments
Open

FileTools has good copy function #13

calvertdw opened this issue Mar 28, 2018 · 0 comments

Comments

@calvertdw
Copy link
Member

calvertdw commented Mar 28, 2018 •
edited
Loading 

         try
         {
            FileTools.ensureDirectoryExists(to.getParent());
            Files.copy(from, to, StandardCopyOption.REPLACE_EXISTING);
         }
         catch (IOException e)
         {
            throw new RuntimeException(e);
         }
ihmc-rosie pushed a commit that referenced this issue Jul 2, 2018
@calvertdw
Merge pull request #13 in LIBS/ihmc-commons from feature/allocation-r…
23020f1 
…ecorder-refactor-2 to develop

* commit '4cb9979d98dadd0ce8cfbaf44a8420bfd0df9a1a':
  Add mutation test.
  Finish documentation.
  More documentation. Fix bug where I set the wrong boolean to true. Add JUnit exclusion (FutureTask.waitOn), rename clear to reset.
  Rename newObject to get allocatedObject. Auto configure excluding everything once an inclusion is added. Start on documentation.
  Move demo to test set.
  Remove AllocationTest interface. Stephen and I agreed it probably was harder to read than just creating and using a profiler.
  Ignore broken switch test and add some debug info.
  Ignore allocations from Gradle when tests are run with Gradle.
  Rewrote included/exclude filters to run faster, have a few more features ("allocations of objects", "keyword based inclusions").
  Ignore flaky test.
  Add test coverage and make code easier to follow.
  In order to make it easier to write and test the specific include/exclude/whitelist/blacklist/interest/ignore logic, create an AllocationRecord to store more information about each allocation in a more organized way. This is just the first stopping point I found. More to come.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@calvertdw