- Sort Score
- Result 10 results
- Languages All
Results 1 - 8 of 8 for sourceSets (0.61 sec)
-
platforms/documentation/docs/src/docs/userguide/api/kotlin_dsl.adoc
* Project extensions and conventions (such as `sourceSets`), and extensions on them * Extensions on the `dependencies` and `repositories` containers, and extensions on them * Elements in the `tasks` and `configurations` containers * Elements in <<kotdsl:containers,project-extension containers>> (for example the source sets contributed by the Java Plugin that are added to the `sourceSets` container) For the main project settings script:
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Apr 22 20:16:10 UTC 2024 - 55.4K bytes - Viewed (0) -
platforms/software/ivy/src/integTest/groovy/org/gradle/api/publish/ivy/IvyPublishJavaIntegTest.groovy
} void "ignores extra artifacts added to configurations"() { given: createBuildScripts(""" task extraJar(type: Jar) { from sourceSets.main.allJava archiveBaseName = "publishTest-extra" } artifacts { implementation extraJar archives extraJar
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed Nov 15 16:36:23 UTC 2023 - 49.8K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/releases/upgrading/upgrading_version_8.adoc
---- plugins { id("java-library") } sourceSets { create("feature") } java { registerFeature("feature") { usingSourceSet(sourceSets["feature"]) } } ---- ====== [.multi-language-sample] ====== .build.gradle [source,groovy] ---- plugins { id("java-library") } sourceSets { feature } java {
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Jun 07 17:01:07 UTC 2024 - 90.7K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/releases/upgrading/upgrading_version_7.adoc
```groovy sourceSets { main { groovy { // ... } } } ``` However, the return type of the groovy block has changed to the extension type. This means that the following snippet no longer works in Gradle 7.1: ```groovy sourceSets { main { GroovySourceSet sourceSet = groovy { // ...
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Apr 01 15:00:23 UTC 2024 - 87.7K bytes - Viewed (0) -
subprojects/diagnostics/src/integTest/groovy/org/gradle/api/tasks/diagnostics/OutgoingVariantsReportTaskIntegrationTest.groovy
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed Mar 13 19:52:38 UTC 2024 - 50K bytes - Viewed (0) -
testing/architecture-test/src/changes/archunit-store/public-api-methods-return-allowed-types.txt
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Jun 07 12:21:31 UTC 2024 - 91.3K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/jvm/java_testing.adoc
The example also does the following, not all of which you may need for your specific integration tests: * Adds the production classes from the `main` source set to the compilation and runtime classpaths of the integration tests — `sourceSets.main.output` is a <<working_with_files.adoc#sec:file_collections,file collection>> of all the directories containing compiled production classes and resources
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Mar 29 16:24:12 UTC 2024 - 53.1K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/optimizing-performance/configuration_cache.adoc
Here's an example of a problematic task type referencing a `SourceSet`: ==== include::sample[dir="snippets/configurationCache/disallowedTypes/kotlin",files="build.gradle.kts[tags=task-type]"] include::sample[dir="snippets/configurationCache/disallowedTypes/groovy",files="build.gradle[tags=task-type]"] ==== <1> this will be reported as a problem because referencing `SourceSet` is not allowed The following is how it should be done instead:
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Mar 29 16:24:12 UTC 2024 - 71.1K bytes - Viewed (0)