title: Best method to analyze external (nexus) dependencies in a "lift and shift" migration move?
body: <p>I'm carrying out a "lift and shift" migration of some functionality from a monolithic java spring application towards a standalone deployable. </p>
  
  <p>The first snag I've run into is the project pulling references (through maven/nexus) to external APIs and not truly highlighting what areas of the codebase are dependent on code that is external to the project. Being that this is a large lift and shift, I need to identify the areas that are external, so I figure out the best way to not need those dependencies. </p>
  
  <p>I've tried playing with the IntelliJ dependency tool, but it seems like it only analyzes dependencies within classes in the project itself. Is there a better tool to identify all the external classes / api's / services my app depends on?</p>