- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 12 for __and__ (0.21 sec)
-
subprojects/core/src/main/java/org/gradle/internal/operations/DefaultBuildOperationQueue.java
// TODO This could be more efficient, so that we only start a worker when there are none idle _and_ there is a worker lease available executor.execute(new WorkerRunnable()); workerCount++; } } finally { lock.unlock(); } }
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Tue Jan 31 15:18:20 UTC 2023 - 10.4K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/jvm/groovy_plugin.adoc
image::groovyPluginTasks.png[] [[sec:groovy_project_layout]] == Project layout
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Nov 27 17:53:42 UTC 2023 - 15.6K bytes - Viewed (0) -
src/test/java/org/codelibs/fess/suggest/SuggesterTest.java
Registered: Wed Jun 12 15:38:08 UTC 2024 - Last Modified: Thu Feb 22 01:36:54 UTC 2024 - 37K bytes - Viewed (0) -
src/cmd/compile/internal/types2/typeset.go
// implied by the methods and the type set described by the terms and the // comparable bit. To test whether a type is included in a type set // ("implements" relation), the type must implement all methods _and_ be // an element of the type set described by the terms and the comparable bit. // If the term list describes the set of all types and comparable is true, // only comparable types are meant; in all other cases comparable is false.
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Thu May 30 19:19:55 UTC 2024 - 13.6K bytes - Viewed (0) -
src/go/types/typeset.go
// implied by the methods and the type set described by the terms and the // comparable bit. To test whether a type is included in a type set // ("implements" relation), the type must implement all methods _and_ be // an element of the type set described by the terms and the comparable bit. // If the term list describes the set of all types and comparable is true, // only comparable types are meant; in all other cases comparable is false.
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Thu May 30 19:19:55 UTC 2024 - 13.7K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/jvm/scala_plugin.adoc
.Scala plugin - tasks image::scalaPluginTasks.png[] [[sec:scala_project_layout]] == Project layout The Scala plugin assumes the project layout shown below. All the Scala source directories can contain Scala _and_ Java code. The Java source directories may only contain Java source code. None of these directories need to exist or have anything in them; the Scala plugin will simply compile whatever it finds. [[scalalayout]]
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed Nov 29 17:38:38 UTC 2023 - 17K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/releases/upgrading/upgrading_version_5.adoc
If you have a Maven dependency pointing to an Ivy dependency where the `default` configuration dependencies do not match the `compile` + `runtime` + `master` ones _and_ that Ivy dependency was substituted (using a `resolutionStrategy.force`, `resolutionStrategy.eachDependency` or `resolutionStrategy.dependencySubstitution`) then this fix will impact you.
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Feb 22 03:01:48 UTC 2024 - 47.5K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/jvm/java_library_plugin.adoc
NOTE: The usage or not of the classes output instead of the JAR is a _consumer_ decision. For example, Groovy consumers will request classes _and_ processed resources as these may be needed for executing AST transformation as part of the compilation process. [[sub:java_library_known_issues_memory]] === Increased memory usage for consumers
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Wed Mar 13 19:52:38 UTC 2024 - 23.3K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/authoring-builds/basics/plugins.adoc
While the default behavior of the `plugins{}` block is to immediately `resolve` _and_ `apply` the plugins, you can use the `apply false` syntax to tell Gradle not to apply the plugin to the current project. Then, use the `plugins{}` block without the version in subprojects' build scripts: ====
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Fri May 31 04:11:37 UTC 2024 - 24.2K bytes - Viewed (0) -
platforms/documentation/docs/src/docs/userguide/dep-man/03-controlling-transitive-dependencies/platforms.adoc
In practice, your project can both use a catalog _and_ declare a platform which itself uses the catalog: .Using a catalog within a platform definition ====
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Mon Feb 05 18:33:11 UTC 2024 - 29.7K bytes - Viewed (0)