snehalmistry/spring-migration-analyzer — comment on commit 95cd33eb2b57c6d53d072022fed5e3caaefabb5d
File:  line 0
By wilkinsona:

Rather than implementing batch analysis as a completely separate entry point into the application, it would be better to implement it as an extension to the existing entry point. This will avoid duplicating a lot of the same logic that already exists for the single case. Also, as things stand, I don't think it's possible to make use of the batch analysis, unless I've missed a change to the .bat and .sh scripts that launch the application.

I think a better approach would be to enhance CommandLineMigrationAnalysisExecutor so that it behaves as it does today if the input is a single archive, but runs multiple scan if the input is a directory: one scan for each archive in the directory. We'd need to tweak the output path a little in the batch case, for example creating a subdirectory for each report that's named after the archive that was scanned.