You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
, the test source set is checked twice with configLocation and testConfigLocation configurations, resulting in unnecessary warnings for test source set since the rules for test source set are less strict in my case.
If I set includeTestSourceDirectory to false, code is checked as expected, the main source set with configLocation config and the test source set with testConfigLocation config.
I suggest that:
either documentation should say that includeTestSourceDirectory = true uses configLocation configuration;
or fix the plugin so includeTestSourceDirectory = true uses testConfigLocation if defined, configLocation otherwise.
The text was updated successfully, but these errors were encountered:
lunaticare
changed the title
Do not check test source set with configuration for main when testConfig location is defined
Do not check test source set with configuration for main when testConfigLocation is defined
Nov 8, 2018
When I use the following configuration:
, the test source set is checked twice with
configLocation
andtestConfigLocation
configurations, resulting in unnecessary warnings for test source set since the rules for test source set are less strict in my case.If I set
includeTestSourceDirectory
to false, code is checked as expected, the main source set withconfigLocation
config and the test source set withtestConfigLocation
config.I suggest that:
includeTestSourceDirectory = true
uses configLocation configuration;includeTestSourceDirectory = true
uses testConfigLocation if defined,configLocation
otherwise.The text was updated successfully, but these errors were encountered: