- Sort Score
- Result 10 results
- Languages All
Results 1 - 4 of 4 for ancestors (0.15 sec)
-
build-logic/integration-testing/src/main/kotlin/gradlebuild.cross-version-tests.gradle.kts
configureIde(TestType.CROSSVERSION) configureTestFixturesForCrossVersionTests() fun configureTestFixturesForCrossVersionTests() { // do not attempt to find projects when the plugin is applied just to generate accessors if (project.name != "gradle-kotlin-dsl-accessors" && project.name != "test" /* remove once wrapper is updated */) { dependencies { "crossVersionTestImplementation"(testFixtures(project(":tooling-api"))) } } }
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Jun 10 06:17:20 UTC 2024 - 4.5K bytes - Viewed (0) -
platforms/core-runtime/stdlib-java-extensions/src/main/java/org/gradle/internal/service/scopes/EventScope.java
import java.lang.annotation.Target; /** * Attached to a listener interface to indicate which scope its events are generated in. * * <p>Events generated in a particular scope are visible to listeners in the same scope and ancestor scopes. * Events are not visible to listeners in descendent scopes. * * <p>This annotation is used primarily to indicate to developers the scopes where this listener are available. There is also
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Jun 10 14:28:48 UTC 2024 - 1.5K bytes - Viewed (0) -
platforms/core-runtime/stdlib-java-extensions/src/main/java/org/gradle/internal/service/scopes/ServiceScope.java
* Services are lifecycled with their scope, and stopped/closed when the scope is closed. * <p> * Services are visible to other services in the same scope and descendent scopes. * Services are not visible to services in ancestor scopes. * <p> * When a service is defined in multiple scopes, the highest scope determines the visibility. * The additional instances of the service in lower scopes "override" the instance from the parent
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Jun 10 14:28:48 UTC 2024 - 1.7K bytes - Viewed (0) -
analysis/analysis-api-fir/src/org/jetbrains/kotlin/analysis/api/fir/symbols/KtFirKotlinPropertySymbol.kt
get() = withValidityAssertion { firSymbol.backingFieldSymbol?.let { builder.callableBuilder.buildBackingFieldSymbol(it) } } // NB: `field` in accessors indicates the property should have a backing field. To see that, though, we need BODY_RESOLVE. override val hasBackingField: Boolean get() = withValidityAssertion {
Registered: Wed Jun 12 09:53:16 UTC 2024 - Last Modified: Tue Jun 11 15:45:42 UTC 2024 - 7.5K bytes - Viewed (0)