Currently only one package name can be supplied , what if resources are spread across multiple packages or what if the code follows barebones mvc (some classes in controller package , some in services package, some in model) . Only those mentioned in the packageName property will be picked up and rest ignored.
Currently only one package name can be supplied , what if resources are spread across multiple packages or what if the code follows barebones mvc (some classes in controller package , some in services package, some in model) . Only those mentioned in the packageName property will be picked up and rest ignored.