- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 24 for focusin (0.23 sec)
-
architecture/standards/0005-introduce-core-ui-architecture-module.md
A downside of this structure is that it is difficult to do focused work on the Gradle UI. ## Decision Introduce a "UI" architecture module to the core platform, and move the user interaction services to this new module. This includes: - Logging and progress services.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Mon Mar 04 23:19:15 GMT 2024 - 1.3K bytes - Viewed (0) -
api/maven-api-core/src/main/java/org/apache/maven/api/services/ModelProblemCollector.java
* an expressive source hint for the model problem. Instead, the source hint is configured by the model builder before * it delegates to other components that potentially encounter problems. Then, the problem reporter can focus on * providing a simple error message, leaving the donkey work of creating a nice model problem to this component. * */ public interface ModelProblemCollector { /** * The collected problems.
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Fri Apr 12 10:50:18 GMT 2024 - 2.5K bytes - Viewed (0) -
manifests/charts/README.md
be used to select a different 'environment'. ## Installing The new installer is intended to be modular and very explicit about what is installed. It has far more steps than the Istio installer - but each step is smaller and focused on a specific feature, and can be performed by different people/teams at different times. It is strongly recommended that different namespaces are used, with different service accounts.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Feb 07 17:53:24 GMT 2024 - 6.7K bytes - Viewed (0) -
architecture/standards/0004-use-a-platform-architecture.md
2024-02-07 ## Context The Gradle code base is essentially a large monolith, without strong internal boundaries. This has a number of negative effects on productivity, including: - Unclear ownership of code. - Difficult to focus on one particular area. - Unintended coupling between areas of the code, including tests. ## Decision Organize the Gradle code base into a set of coarse-grained "architecture modules".
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) -
architecture-standards/0004-use-a-platform-architecture.md
2024-02-07 ## Context The Gradle code base is essentially a large monolith, without strong internal boundaries. This has a number of negative effects on productivity, including: - Unclear ownership of code. - Difficult to focus on one particular area. - Unintended coupling between areas of the code, including tests. ## Decision Organize the Gradle code base into a set of coarse-grained "architecture modules".
Plain Text - Registered: Wed Feb 14 11:36:15 GMT 2024 - Last Modified: Wed Feb 07 00:56:13 GMT 2024 - 4.5K bytes - Viewed (0) -
maven-api-impl/src/main/java/org/apache/maven/internal/impl/model/DefaultModelProblemCollector.java
* an expressive source hint for the model problem. Instead, the source hint is configured by the model builder before * it delegates to other components that potentially encounter problems. Then, the problem reporter can focus on * providing a simple error message, leaving the donkey work of creating a nice model problem to this component. * */ class DefaultModelProblemCollector implements ModelProblemCollector {
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Fri Apr 12 10:50:18 GMT 2024 - 6.3K bytes - Viewed (0) -
docs/en/docs/tutorial/dependencies/index.md
## First Steps Let's see a very simple example. It will be so simple that it is not very useful, for now. But this way we can focus on how the **Dependency Injection** system works. ### Create a dependency, or "dependable" Let's first focus on the dependency. It is just a function that can take all the same parameters that a *path operation function* can take: === "Python 3.10+"
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 11.6K bytes - Viewed (0) -
README.md
[![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/4898/badge)](https://bestpractices.coreinfrastructure.org/projects/4898)
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sun Mar 24 20:49:08 GMT 2024 - 3.9K bytes - Viewed (0) -
docs/hotfixes.md
# Introduction This document outlines how to make hotfix binaries and containers for MinIO?. The main focus in this article is about how to backport patches to a specific branch and finally building binaries/containers. ## Pre-pre requisite - A working knowledge of MinIO codebase and its various components. - A working knowledge of AWS S3 API behaviors and corner cases. ## Pre-requisite for backporting any fixes
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Feb 14 21:36:02 GMT 2024 - 5K bytes - Viewed (0) -
docs/en/docs/advanced/websockets.md
This, of course, is not optimal and you wouldn't use it for production. In production you would have one of the options above. But it's the simplest way to focus on the server-side of WebSockets and have a working example: ```Python hl_lines="2 6-38 41-43" {!../../../docs_src/websockets/tutorial001.py!} ``` ## Create a `websocket`
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 6.2K bytes - Viewed (0)