The new DocBook plugin requires that the sourceFileName property is configured. See gh-9
The -t option may now be specified multiple times, allowing both an XML report and an HTML report to be produced at the same time.
Prior to this commit, each report was written into a directory with the same name as its input archive. This meant that, if the output path was the same directory as the one that contained the input archive, their names would clash. To overcome this problem, each report is now written into a directory with a name of the form migration-analysis-<input-archive>. For example, if my-app.ear is analysed, its report will be written into a directory named migration-analysis-my-app.ear. In addition to the change described above, each report directory now contains a subdirectory for the report type. Continuing the example above, if an HTML report is produced it will be found in a directory named migration-analysis-my-app.ear/html. This paves the way for rendering multiple reports from the same analysis (SMA-3). For example, it's currently expected that analysing my-app.ear with reports in format1 and format2 would produce the following: migration-analysis-my-app.ear/ format1/ … format2/ …
Convert the build system from Gradle to Maven. This has had the side-effect of forcing some code changes to be made: Some test code has been changed to cope with Gradle's use of <project>/build (on the command line) and <project>/bin (in Eclipse) for build output, as opposed to Maven's use of <project>/target The move to Gradle has also moved code coverage from Clover to Jacoco as, in a Gradle environment, Jacoco's Sonar integration is better. There are some differences between the coverage numbers reported by Jacoco and Clover. As a result, some code has been reworked to improve its test coverage.