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
Copy file name to clipboardExpand all lines: README.md
+13-1Lines changed: 13 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,16 @@ The previous definition would make examples and performance SourceSets, so that
33
33
34
34
That will cause the functionalCompile to extend from testCompile, and functionalRuntime to extend from testRuntime, since those are the configurations from the "test" SourceSet.
35
35
36
+
The source directory defaults to the name of the facet, but this can be overridden if necessary, e.g.
37
+
38
+
facets {
39
+
performance {
40
+
srcDir = 'perf'
41
+
}
42
+
}
43
+
44
+
This will create a performance SourceSet for code contained in src/perf/java.
45
+
36
46
Test Facets
37
47
--------------
38
48
@@ -42,12 +52,13 @@ If "Test" is in the facet name, then a Test task would be created (though it'll
42
52
integTest
43
53
}
44
54
45
-
This will create a test task called integTest in addition to the integTest SourceSet. The parent SourceSet can still be overriden like above, and the task name can be set:
55
+
This will create a test task called integTest in addition to the integTest SourceSet. The parent SourceSet can still be overriden like above, and the task name and source directory can be set:
46
56
47
57
facets {
48
58
integTest {
49
59
parentSourceSet = 'main'
50
60
testTaskName = 'integrationTest'
61
+
srcDir = 'integ-test'
51
62
}
52
63
}
53
64
@@ -57,6 +68,7 @@ Test facets may opt out of a dependency on the 'check' task by using `includeInC
0 commit comments