- Sort Score
- Result 10 results
- Languages All
Results 141 - 150 of 4,346 for module$ (0.22 sec)
-
src/cmd/go/testdata/script/mod_symlink.txt
env GO111MODULE=on [!symlink] skip # 'go get' should resolve modules of imported packages. go get go list -deps -f '{{.Module}}' . stdout golang.org/x/text go get ./subpkg go list -deps -f '{{.Module}}' ./subpkg stdout golang.org/x/text # Create a copy of the module using symlinks in src/links. mkdir links symlink links/go.mod -> $GOPATH/src/go.mod symlink links/go.sum -> $GOPATH/src/go.sum
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Tue Sep 28 17:19:14 UTC 2021 - 1.1K bytes - Viewed (0) -
platforms/software/dependency-management/src/integTest/groovy/org/gradle/integtests/resolve/ForcedModulesIntegrationTest.groovy
run("api:dependencies", "tool:dependencies") } void "can force arbitrary version of a module and avoid conflict"() { mavenRepo.module("org", "foo", '1.3.3').publish() mavenRepo.module("org", "foobar", '1.3.3').publish() mavenRepo.module("org", "foo", '1.4.4').publish() mavenRepo.module("org", "foo", '1.5.5').publish() createDirs("api", "impl", "tool")
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Oct 24 06:54:47 UTC 2023 - 7.1K bytes - Viewed (0) -
platforms/ide/ide-plugins/src/integTest/resources/org/gradle/plugins/ide/eclipse/EclipseIntegrationTest/canCreateAndDeleteMetaData/expectedFiles/webserviceWtpComponent.xml
<project-modules id="moduleCoreId" project-version="1.5.0"> <wb-module deploy-name="webservice"> <property name="context-root" value="webservice"/> <wb-resource deploy-path="/WEB-INF/classes" source-path="src/main/java"/> <dependent-module archiveName="api-1.0.jar" deploy-path="/WEB-INF/lib" handle="module:/resource/api/api"> <dependency-type>uses</dependency-type> </dependent-module> </wb-module>
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Nov 13 19:33:30 UTC 2023 - 472 bytes - Viewed (0) -
src/cmd/go/testdata/script/mod_run_pkg_version.txt
[short] skip # 'go run pkg@version' works outside a module. env GO111MODULE=auto go run example.com/cmd/a@v1.0.0 stdout '^a@v1.0.0$' # 'go run pkg@version' reports an error if modules are disabled. env GO111MODULE=off ! go run example.com/cmd/a@v1.0.0 stderr '^go: modules disabled by GO111MODULE=off; see ''go help modules''$' env GO111MODULE=on
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Thu Mar 21 17:25:54 UTC 2024 - 4.4K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/dep-man/dependency_management_terminology.adoc
[[sub::terminology_platform]] == Platform A platform is a set of modules aimed to be used together. There are different categories of platforms, corresponding to different use cases: - module set: often a set of modules published together as a whole. Using one module of the set often means we want to use the same version for all modules of the set. For example, if using `groovy` 1.2, also use `groovy-json` 1.2.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Dec 01 18:45:05 UTC 2023 - 11.5K bytes - Viewed (0) -
testing/internal-integ-testing/src/main/groovy/org/gradle/test/fixtures/ivy/IvyFileModule.groovy
@Override IvyModule dependencyConstraint(Module target) { dependencyConstraints << [organisation: target.group, module: target.module, revision: target.version] return this } @Override IvyModule dependencyConstraint(Map<String, ?> attributes, Module module) { def allAttrs = [organisation: module.group, module: module.module, revision: module.version] allAttrs.putAll(attributes)
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Apr 04 07:21:38 UTC 2024 - 23.9K bytes - Viewed (0) -
platforms/software/dependency-management/src/integTest/groovy/org/gradle/integtests/resolve/ivy/IvyDynamicRevisionRemoteResolveIntegrationTest.groovy
def expectGetDynamicRevision(IvyHttpModule module) { expectListVersions(module) module.ivy.expectGet() module.jar.expectGet() } def expectGetDynamicRevisionMetadata(IvyHttpModule module) { expectListVersions(module) module.ivy.expectGet() } private expectListVersions(IvyHttpModule module) {
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Oct 10 21:10:11 UTC 2023 - 41.4K bytes - Viewed (0) -
src/cmd/go/testdata/script/mod_get_nopkgs.txt
cd subdir # 'go get' on empty patterns that are necessarily local to the module # should warn that the patterns are empty, exactly once. go get ./... stderr -count=1 'matched no packages' go get ./... stderr -count=1 'matched no packages' # 'go get' on patterns that could conceivably match nested modules # should report a module resolution error. go get example.net/emptysubdir/... # control case
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Tue Sep 28 17:19:14 UTC 2021 - 1.3K bytes - Viewed (0) -
platforms/documentation/docs/src/samples/java/modules-multi-project-with-integration-tests/README.adoc
Here, we add an additional source set _integrationTest_ with a `module-info.java`. ``` src └── integrationTest └── java └── module-info.java ``` We effectively declare a second module that is only used for testing. The module is `open`, which means that it allows reflective access to its classes at runtime as required by JUnit's test execution engine. ``` open module org.gradle.sample.integtest.utilities {
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Nov 27 17:53:42 UTC 2023 - 1.8K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/dep-man/06-publishing/publishing_gradle_module_metadata.adoc
_performance optimization_: instead of having to do 2 network requests, one to get Gradle Module Metadata, then one to get the POM/Ivy file in case of a miss, Gradle will first look at the file which is most likely to be present, then only perform a 2nd request if the module was actually published with Gradle Module Metadata. If you know that the modules you depend on are always published with Gradle Module Metadata, you can optimize the network calls by configuring the metadata sources for...
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri Dec 01 18:45:05 UTC 2023 - 9.6K bytes - Viewed (0)