- Sort Score
- Num 10 results
- Language All
Results 1 - 10 of 572 for need (0.02 seconds)
-
impl/maven-core/plugin-manager.txt
h3. Other issues We need to look at Maven, and Nexus as use cases and figure out what each of them needs to be able to do * now what is really the difference between this and loading a component in plexus * do we want a model for sharing information among plugins, is this more like an extension point * do we need a sort of bus for application data
Created: Sun Dec 28 03:35:09 GMT 2025 - Last Modified: Wed Jan 22 11:03:29 GMT 2025 - 12.3K bytes - Click Count (0) -
internal/bucket/bandwidth/reader.go
} else { // part of header can be accommodated r.opts.HeaderSize -= b - 1 need = 1 // to ensure we read at least one byte for every Read tokens = b } } else { // all tokens go towards payload need = int(math.Min(float64(b), float64(need))) tokens = need } // reduce tokens requested according to availability av := int(r.throttle.Tokens()) if av < tokens && av > 0 { tokens = avCreated: Sun Dec 28 19:28:13 GMT 2025 - Last Modified: Sun Sep 28 20:59:21 GMT 2025 - 3.3K bytes - Click Count (0) -
impl/maven-core/src/site/apt/getting-to-container-configured-mojos.apt
DefaultExpressionEvaluator used within. See the above discussion for more on why this evaluator is bad. We need to provide either an alternative implementation under a different roleHint, or else replace the BasicComponentConfigurator. * Other We may need to define a new lifecycle/phase to contextualize a mojo right before it's used, and reset it's state afterward. Up to now, the approach
Created: Sun Dec 28 03:35:09 GMT 2025 - Last Modified: Fri Oct 25 12:31:46 GMT 2024 - 4.1K bytes - Click Count (0) -
architecture/standards/0006-use-of-provider-apis-in-gradle.md
## Consequences * We are incurring debt that will need to be paid later via deprecations or breaking changes to existing classes. The implementation for some Gradle types will be more complicated than an equivalent clean-sheet implementation. * During code reviews that introduce new APIs, reviewers need to be mindful that all new properties are implemented with lazy types.
Created: Wed Dec 31 11:36:14 GMT 2025 - Last Modified: Tue Oct 15 20:00:57 GMT 2024 - 10K bytes - Click Count (0) -
docs/en/docs/tutorial/path-params-numeric-validations.md
/// ## Order the parameters as you need { #order-the-parameters-as-you-need } /// tip This is probably not as important or necessary if you use `Annotated`. /// Let's say that you want to declare the query parameter `q` as a required `str`. And you don't need to declare anything else for that parameter, so you don't really need to use `Query`.Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Wed Dec 17 20:41:43 GMT 2025 - 6.1K bytes - Click Count (0) -
ci/official/utilities/setup_macos.sh
chmod +x "/usr/local/bin/bazel" fi # "TFCI_MACOS_UPGRADE_PYENV_ENABLE" is used to decide if we need to upgrade the # Pyenv version. We enable this for macOS x86 builds as the default Pyenv on # those VMs does not support installing Python 3.12 and above which we need # for running smoke tests in nightly/release wheel builds. if [[ "${TFCI_MACOS_UPGRADE_PYENV_ENABLE}" == 1 ]]; then echo "Upgrading pyenv..."
Created: Tue Dec 30 12:39:10 GMT 2025 - Last Modified: Mon Oct 06 22:42:26 GMT 2025 - 6.8K bytes - Click Count (0) -
docs/en/docs/advanced/using-request-directly.md
Up to now, you have been declaring the parts of the request that you need with their types. Taking data from: * The path as parameters. * Headers. * Cookies. * etc. And by doing so, **FastAPI** is validating that data, converting it and generating documentation for your API automatically. But there are situations where you might need to access the `Request` object directly.
Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Wed Dec 17 20:41:43 GMT 2025 - 2.4K bytes - Click Count (0) -
architecture/standards/0003-avoid-introducing-Groovy-types-to-public-api.md
Doing this provides the following specific benefits: - **Reduce the API surface** - We no longer need to maintain two methods. - **Consistency** - All languages have consistent access to the same APIs and ergonomics in the DSL. - **Reduce the size of the Gradle distribution** - We no longer need to carry multiple standard libraries for different languages. ## Decision
Created: Wed Dec 31 11:36:14 GMT 2025 - Last Modified: Sun Mar 10 20:38:06 GMT 2024 - 1.8K bytes - Click Count (0) -
docs/en/docs/tutorial/background-tasks.md
## Caveat { #caveat } If you need to perform heavy background computation and you don't necessarily need it to be run by the same process (for example, you don't need to share memory, variables, etc), you might benefit from using other bigger tools like <a href="https://docs.celeryq.dev" class="external-link" target="_blank">Celery</a>.Created: Sun Dec 28 07:19:09 GMT 2025 - Last Modified: Wed Dec 17 20:41:43 GMT 2025 - 4.8K bytes - Click Count (0) -
impl/maven-core/src/main/java/org/apache/maven/lifecycle/MavenExecutionPlan.java
import org.apache.maven.plugin.descriptor.MojoDescriptor; // TODO lifecycles being executed // TODO what runs in each phase // TODO plugins that need downloading // TODO project dependencies that need downloading // TODO unfortunately the plugins need to be downloaded in order to get the plugin.xml file. need to externalize this // from the plugin archive. // TODO this will be the class that people get in IDEs to modify /**
Created: Sun Dec 28 03:35:09 GMT 2025 - Last Modified: Fri Jun 06 14:28:57 GMT 2025 - 6.3K bytes - Click Count (0)