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
necessary for further commits
MAIN:
1) renamed TestModuleOptions.isRunOnClasspath() to getRunOnClasspath() (otherwise won't work with Kotlin DSL) + added a Kotlin DSL example for "runOnClasspath = true" to README.md
2) introduced JavaProjectHelper and applied it to CompileTask
3) added comments for all anonymous classes that should not be removed
4) minor improvements in ModuleSystemPlugin
5) minor fixes in test-project-kotlin/README.md
TEST:
1) bumped smoke-test Gradle version to 5.0 (for improved Kotlin DSL)
2) introduced a no-op "moduleOptions" access in greeter.api (for testing DSL)
3) introduced SmokeTestHelper for ModulePluginSmokeTest
4) disabled stackTraceFilters in all tests
5) updated Kotlin to 1.3.20
Copy file name to clipboardExpand all lines: README.md
+21-2
Original file line number
Diff line number
Diff line change
@@ -265,7 +265,10 @@ See `src/test/java/module-info.test` and `src/test/java/greeter/ScriptingTest.ja
265
265
Fall-back to classpath mode
266
266
----
267
267
268
-
If for whatever reason this is unwanted or introduces problems, you can enable classpath mode, which essentially turns of the plugin while running tests.
268
+
If for whatever reason this is unwanted or introduces problems, you can enable classpath mode, which essentially turns off the plugin while running tests.
269
+
270
+
<detailsopen>
271
+
<summary>Groovy DSL</summary>
269
272
270
273
```groovy
271
274
test {
@@ -275,6 +278,22 @@ test {
275
278
}
276
279
```
277
280
281
+
</details>
282
+
<details>
283
+
<summary>Kotlin DSL</summary>
284
+
285
+
```kotlin
286
+
tasks {
287
+
test {
288
+
extensions.configure(TestModuleOptions::class) {
289
+
runOnClasspath =true
290
+
}
291
+
}
292
+
}
293
+
```
294
+
295
+
</details>
296
+
278
297
Blackbox testing
279
298
===
280
299
@@ -286,7 +305,7 @@ This module `requires` and/or `uses` the module under test, and tests it's exter
286
305
In the following example we test a module `greeter.provider`, which provides a service implementation of type `Greeter`.
287
306
The `Greeter` type is provided by yet another module `greeter.api`.
288
307
289
-
The test module would typically be named something similar to the the module it's testing, e.g. `greeter.provider.test`.
308
+
The test module would typically be named something similar to the module it's testing, e.g. `greeter.provider.test`.
290
309
In `src/main/java` it has some code that looks like code that you would normally write to use the module that's being tested.
0 commit comments