- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 90 for MODULES (0.24 sec)
-
build-logic/dependency-modules/src/main/kotlin/gradlebuild.dependency-modules.gradle.kts
params(name) params("${providedBy.size + 1}") } } /** * For all modules providing a capability, always use the preferred module, even if there's no conflict. * In other words, will forcefully upgrade all modules providing a capability to a selected module. * * @param to the preferred module */ private
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Wed Aug 24 23:27:45 GMT 2022 - 9.1K bytes - Viewed (0) -
maven-core/src/test/resources/projects/transform/after.pom
<configuration> <modules> <module> <test>test</test> </module> <jarModule> <groupId>artifactGroupId</groupId> <artifactId>artifactId</artifactId> <uri>APP-INF/lib/anotherName-1.2.3.jar</uri> </jarModule> </modules> </configuration> </plugin>
Plain Text - Registered: Sun Mar 31 03:35:09 GMT 2024 - Last Modified: Thu Sep 14 07:51:37 GMT 2023 - 2.4K bytes - Viewed (0) -
src/README.vendor
Vendoring in std and cmd ======================== The Go command maintains copies of external packages needed by the standard library in the src/vendor and src/cmd/vendor directories. There are two modules, std and cmd, defined in src/go.mod and src/cmd/go.mod. When a package outside std or cmd is imported by a package inside std or cmd, the import path is interpreted as if it had a "vendor/" prefix. For example, within "crypto/tls",
Plain Text - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Tue Apr 02 02:20:05 GMT 2024 - 2.2K bytes - Viewed (0) -
maven-core/src/test/resources/projects/transform/before.pom
<groupId>test</groupId> <artifactId>test</artifactId> <version>0.1-SNAPSHOT</version> <packaging>pom</packaging> <modules> <module>lib</module> <!-- the library --> <module>app</module> <!-- the application --> </modules> <build> <pluginManagement> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId>
Plain Text - Registered: Sun Mar 31 03:35:09 GMT 2024 - Last Modified: Thu Sep 14 07:51:37 GMT 2023 - 3.5K bytes - Viewed (0) -
architecture/runtimes.md
Most source code targets the daemon and the remaining code either targets a single runtime, for example the Gradle client, or is shared across multiple runtimes. ## Composition by architecture modules Each [architecture module and platform](platforms.md) can contribute code to any of the runtimes. Not every module contributes to every runtime. The core-runtime module defines each runtime:
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 06:42:46 GMT 2024 - 2.3K bytes - Viewed (0) -
maven-core/src/test/resources/apiv4-repo/org/apache/maven/wagon/wagon-providers/1.0-beta-2/wagon-providers-1.0-beta-2.pom
<version>1.0-beta-2</version> </parent> <modelVersion>4.0.0</modelVersion> <artifactId>wagon-providers</artifactId> <packaging>pom</packaging> <name>Maven Wagon Providers Parent</name> <modules> <module>wagon-file</module> <module>wagon-ftp</module> <module>wagon-http-lightweight</module> <module>wagon-http</module> <module>wagon-http-shared</module> <module>wagon-ssh-external</module>
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Oct 02 08:41:25 GMT 2022 - 1.7K bytes - Viewed (0) -
analysis/analysis-api-fir/src/org/jetbrains/kotlin/analysis/api/fir/KtFirAnalysisSessionProvider.kt
override fun afterInvalidation(modules: Set<KtModule>) { modules.forEach { analysisSessionProvider.cache.remove(it) } } override fun afterGlobalInvalidation() { // Session invalidation events currently don't report whether library modules were included in the global invalidation. This is
Plain Text - Registered: Fri Apr 26 08:18:10 GMT 2024 - Last Modified: Thu Apr 18 10:43:08 GMT 2024 - 5.1K bytes - Viewed (0) -
architecture/standards/0004-use-a-platform-architecture.md
## Decision Organize the Gradle code base into a set of coarse-grained "architecture modules". An architecture module is responsible for providing a coherent set of features and: - Provides a set of APIs and services for use from outside the module. - Has a private implementation. - Is owned by a single team. A team may own multiple architecture modules. The modules are arranged into several different "Gradle platforms".
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sun Feb 25 22:19:29 GMT 2024 - 4.5K bytes - Viewed (0) -
.gitignore
!**/testData/**/*.iml .idea/artifacts .idea/remote-targets.xml .idea/libraries/Gradle*.xml .idea/libraries/Maven*.xml .idea/modules .idea/runConfigurations/JPS_*.xml .idea/runConfigurations/_JPS_*.xml .idea/runConfigurations/PILL_*.xml .idea/runConfigurations/_FP_*.xml .idea/runConfigurations/_MT_*.xml .idea/libraries .idea/modules.xml .idea/gradle.xml .idea/compiler.xml .idea/inspectionProfiles/profiles_settings.xml .idea/.name
Plain Text - Registered: Fri May 03 08:18:13 GMT 2024 - Last Modified: Wed Feb 21 15:38:02 GMT 2024 - 1.2K bytes - Viewed (0) -
architecture/platforms.md
--> # Gradle platform architecture Gradle is arranged into coarse-grained components called "architecture modules" and "platforms". See [ADR4](standards/0004-use-a-platform-architecture.md) for a definition of these terms. The diagram below shows the current set of architecture modules and platforms: <!-- This diagram is generated. Use `./gradlew :architectureDoc` to update it --> ```mermaid graph TD
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 06:42:46 GMT 2024 - 5.4K bytes - Viewed (0)