so far users are forced to repeat @AnalyzeClasses annotation an every test class. This cause additional maintenance overhead when common properties (e.g. package structure) changes. To support the DRY approach, @AnalzyeClasses annotation can now be used as meta annotation.
so far users are forced to repeat
@AnalyzeClasses
annotation an every test class. This cause additional maintenance overhead when common properties (e.g. package structure) changes. To support the DRY approach,@AnalzyeClasses
annotation can now be used as meta annotation.Resolves: #182