- Sort Score
- Result 10 results
- Languages All
Results 51 - 60 of 1,268 for logic (0.1 sec)
-
build-logic/documentation/build.gradle.kts
plugins { id("gradlebuild.build-logic.kotlin-dsl-gradle-plugin") id("gradlebuild.build-logic.groovy-dsl-gradle-plugin") } description = "Provides a plugin to generate Gradle's DSL reference, User Manual and Javadocs" dependencies { implementation("gradlebuild:basics") implementation("gradlebuild:module-identity") implementation(project(":build-update-utils")) implementation("com.github.javaparser:javaparser-core")
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Sat Sep 30 16:17:28 UTC 2023 - 1.2K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/img/software_architecture.puml
database "External Repository" { [Spring Boot\nFramework] as SpringBoot [Android\nFramework] as Android } package "Application Layer" { [server-application] [android-app] } package "Business Logic Layer" { [user-feature] [admin-feature] } package "Domain Model Layer" { [domain-model] <-right- [state] } [server-application] -down-> [user-feature] [server-application] -down-> [admin-feature]
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Nov 27 17:53:42 UTC 2023 - 886 bytes - Viewed (0) -
platforms/core-configuration/declarative-dsl-provider/src/integTest/groovy/org/gradle/internal/declarativedsl/project/DeclarativeDslProjectBuildFileIntegrationSpec.groovy
} } } """ file(extensionFile) << extensionCode file("build-logic/src/main/java/com/example/restricted/SoftwareTypeRegistrationPlugin.java") << defineSettingsPluginRegisteringSoftwareTypeProvidingPlugin() file("build-logic/src/main/java/com/example/restricted/RestrictedPlugin.java") << """ package com.example.restricted;
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu May 30 12:25:47 UTC 2024 - 12.9K bytes - Viewed (0) -
analysis/analysis-api-impl-base/src/org/jetbrains/kotlin/analysis/api/impl/base/substitutorMarkers.kt
import org.jetbrains.kotlin.analysis.api.symbols.KaTypeParameterSymbol import org.jetbrains.kotlin.analysis.api.types.KaSubstitutor import org.jetbrains.kotlin.analysis.api.types.KaType /** * A [KaSubstitutor] which substitution logic can be represented as a [Map] from a [KaTypeParameterSymbol] to corresponding [KaType] * This is an implementation details and Analysis API clients should not depend on the fact if some [KaSubstitutor] is [KaMapBackedSubstitutor] or not.
Registered: Wed Jun 12 09:53:16 UTC 2024 - Last Modified: Wed May 22 06:28:34 UTC 2024 - 1.4K bytes - Viewed (0) -
src/cmd/cgo/internal/testfortran/fortran_test.go
if strings.Contains(fc, "gfortran") { // TODO: This duplicates but also diverges from logic from cmd/go // itself. For example, cmd/go merely adds -lgfortran without the extra // library path work. If this is what's necessary to run gfortran, we // should reconcile the logic here and in cmd/go.. Maybe this should // become a cmd/go script test to share that logic. // Add -m32 if we're targeting 386, in case this is a cross-compile.
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Wed Oct 18 01:29:16 UTC 2023 - 2.6K bytes - Viewed (0) -
docs/en/docs/advanced/events.md
# Lifespan Events You can define logic (code) that should be executed before the application **starts up**. This means that this code will be executed **once**, **before** the application **starts receiving requests**. The same way, you can define logic (code) that should be executed when the application is **shutting down**. In this case, this code will be executed **once**, **after** having handled possibly **many requests**.
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Thu Apr 18 19:53:19 UTC 2024 - 7.8K bytes - Viewed (0) -
build-logic/performance-testing/build.gradle.kts
plugins { id("gradlebuild.build-logic.kotlin-dsl-gradle-plugin") id("gradlebuild.build-logic.groovy-dsl-gradle-plugin") } description = "Provides a plugin for generating and defining performance test projects" dependencies { implementation("gradlebuild:basics") implementation("gradlebuild:module-identity") implementation(project(":integration-testing")) implementation(project(":cleanup"))
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed Apr 03 13:29:44 UTC 2024 - 1.4K bytes - Viewed (0) -
platforms/software/dependency-management/src/integTest/groovy/org/gradle/integtests/resolve/transform/UndeclaredDependencyResolutionIntegrationTest.groovy
when: run("broken") then: assertTransformed() output.contains("result = [a.jar.green, b.jar.green]") } @UnsupportedWithConfigurationCache(because = "task dependency logic is not executed when loaded from the configuration cache") def "can query FileCollection containing the output of transform of project artifacts at task graph calculation time"() { setupBuildWithProjectArtifactTransforms()
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Oct 24 06:54:47 UTC 2023 - 12.4K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/authoring-builds/best-practices/organizing_gradle_projects.adoc
├── settings.gradle ├── subproject-one │ └── build.gradle └── subproject-two └── build.gradle ---- ===== ==== [[sec:build_sources]] == Use `buildSrc` to abstract imperative logic Complex build logic is usually a good candidate for being encapsulated either as custom task or binary plugin. Custom task and plugin implementations should not live in the build script.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Apr 23 08:16:36 UTC 2024 - 13.1K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/authoring-builds/tasks/controlling_task_execution.adoc
} dependencies { implementation(project(':some-logic')) // dependency on some-logic } ---- ===== ==== If we run `:app:build` again, we see the Java code of `some-logic` is also compiled by Gradle automatically: [source,text] ---- $./gradlew :app:build > Task :app:processResources NO-SOURCE > Task :app:processTestResources NO-SOURCE
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Sat Mar 23 22:37:03 UTC 2024 - 14.2K bytes - Viewed (0)