- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 40 for have (0.27 sec)
-
build-logic-commons/gradle-plugin/src/main/kotlin/gradlebuild/testcleanup/extension/TestFilesCleanupBuildServiceRootExtension.kt
package gradlebuild.testcleanup.extension import org.gradle.api.provider.MapProperty import org.gradle.api.provider.Property import java.io.File /** * An extension to work with {@see TestFilesCleanupService}. * We have to collect all information we need in this extension and pass them * to the build service. */ interface TestFilesCleanupBuildServiceRootExtension { val projectStates: MapProperty<String, TestFilesCleanupProjectState>
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Mon Aug 22 08:53:41 GMT 2022 - 1.2K bytes - Viewed (0) -
.github/workflows/pull-metadata.yml
types: [ closed ] permissions: {} jobs: check_pull_metadata: permissions: issues: write pull-requests: write runs-on: ubuntu-latest steps: # Check that PRs have proper metadata: labels and milestone # https://github.com/gradle/issue-management-action/blob/main/src/pull-metadata.ts - uses: gradle/issue-management-action@v1 with:
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 09:13:16 GMT 2024 - 477 bytes - Viewed (0) -
.teamcity/README.md
If you have ktlint errors, you can automatically fix them by running `mvn com.github.gantsign.maven:ktlint-maven-plugin:1.1.1:format`. ## How the configuration works We use Kotlin portable DSL to store TeamCity configuration, which means you can easily create a new pipeline based on a specific branch. Currently, we have two pipelines: `master` and `release`, but you can easily create
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Wed Mar 06 23:02:25 GMT 2024 - 4K bytes - Viewed (0) -
.cm/lacks_tests.cm
# can also use the constant `true` if you want to always run the actions. # Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 2.4K bytes - Viewed (0) -
build-logic/documentation/src/main/groovy/gradlebuild/docs/dsl/source/ExtractDslMetaDataTask.groovy
//updating/modifying the metadata and making sure every type reference across the metadata is fully qualified //so, the superClassName, interfaces and types needed by declared properties and declared methods will have fully qualified name TypeNameResolver resolver = new TypeNameResolver(repository) repository.each { name, metaData -> fullyQualifyAllTypeNames(metaData, resolver) }
Groovy - Registered: Wed Apr 17 11:36:08 GMT 2024 - Last Modified: Mon Jan 08 12:45:57 GMT 2024 - 4.4K bytes - Viewed (0) -
build-logic/documentation/src/main/groovy/gradlebuild/docs/GradleDocumentationExtension.java
*/ public abstract ConfigurableFileCollection getClasspath(); /** * A working directory to be used to stage documentation as its generated. * All of the sections of the documentation have working directories off of this one. */ public abstract DirectoryProperty getStagingRoot(); /** * The final location to place all rendered documentation. */
Java - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Fri Aug 11 08:52:40 GMT 2023 - 4.4K bytes - Viewed (0) -
.cm/add_usual_expert.cm
# can also use the constant `true` if you want to always run the actions. # Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.4K bytes - Viewed (0) -
Development.md
2. That should be it. The suggestion will be displayed in the "Try" section. ### Remove generic suggestions For some scenarios, it doesn't make sense to display all the generic suggestions we currently have. E.g. `--stacktrace` for a compilation error is not helpful. To influence the generic suggestions Gradle displays, the NonGradleCause interface was introduced.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Tue Feb 06 22:54:40 GMT 2024 - 1.8K bytes - Viewed (0) -
.cm/complex_changes.cm
# can also use the constant `true` if you want to always run the actions. # Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.7K bytes - Viewed (0) -
build-logic/documentation/src/main/groovy/gradlebuild/docs/dsl/docbook/model/ClassDoc.groovy
} return sections[0] } Element getDescription() { if (comment.isEmpty() || comment[0].tagName != 'para') { throw new RuntimeException("Class $className does not have a description paragraph.") } return comment[0] } PropertyDoc findProperty(String name) { return classProperties.find { it.name == name } }
Groovy - Registered: Wed Apr 17 11:36:08 GMT 2024 - Last Modified: Wed Dec 09 08:14:05 GMT 2020 - 6.2K bytes - Viewed (0)