Feature: Change references to migration utils classes to reference Baton utils classes in anticipation of new Baton release

[cpointe-ibllanos]

Description

In order to allow Baton migrations to be more reusable and general, we should pull out key features from aiSSEMBLE foundation-upgrade and move them directly into baton so they can be extended.

Related issue on the Baton side

DOD

This ticket will focus on moving an initial utils class from aiSSEMBLE from com.boozallen.aissemble.upgrade to Baton in order to set the pattern for the remaining classes FileUtils.java will be migrated from aiSSEMBLE to Baton

• Migrate utility in the Baton repo
  • Remove mentions of aiSSEMBLE if present
• Identify and write unit tests for the relevant util methods
• Verify the migrated utility works in Baton
  • Update test steps and run through them
• Update the documentation for Baton to illustrate the new capability
  • Update javadoc description if needed
  • Add an example project in baton directory that uses utils to do a simple migration
• Nice to have: move MigrationUtils.java to Baton (It's super bare-bones and simple)

Test Strategy/Script

h2. Test Steps

1. Pull down and open Baton
   git clone [email protected]:TechnologyBrewery/baton
2. Confirm the Baton bootstrap build is successful and tests pass
   mvn clean install -Pbootstrap
3. Confirm the Baton example projects build successfully
   mvn clean install
4. Pull down and open aiSSEMBLE
   git clone [email protected]:boozallen/aissemble
5. Checkout the branch for this ticket
   git checkout #176
6. Run the baton migration unit tests successfully
   ./mvnw clean install -pl :foundation-upgrade