- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 639 for needn (0.03 sec)
-
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
Registered: Sun Nov 03 03:35:11 UTC 2024 - Last Modified: Fri Oct 25 12:31:46 UTC 2024 - 12.9K bytes - Viewed (0) -
docs/en/docs/how-to/configure-swagger-ui.md
] ``` These are **JavaScript** objects, not strings, so you can't pass them from Python code directly.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sat Oct 26 16:50:52 UTC 2024 - 2.7K bytes - Viewed (0) -
docs/en/docs/virtual-environments.md
* ``` /// ## Install Packages After activating the environment, you can install packages in it. /// tip Do this **once** when installing or upgrading the packages your project needs. If you need to upgrade a version or add a new package you would **do this again**. /// ### Install Packages Directly
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sat Aug 24 03:16:23 UTC 2024 - 21.7K bytes - Viewed (0) -
architecture/ambient/ztunnel.md
## Configuration protocol Ztunnel, of course, needs to be dynamically configured in order to make decisions on how it should handle traffic. For this purpose, we chose to use xDS transport protocol due to our expertise and existing infrastructure, and because the protocol is well suited to our needs.
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Wed Jul 17 23:10:17 UTC 2024 - 16.8K bytes - Viewed (0) -
docs/en/docs/tutorial/query-params.md
"needy" ], "msg": "Field required", "input": null, "url": "https://errors.pydantic.dev/2.1/v/missing" } ] } ``` As `needy` is a required parameter, you would need to set it in the URL: ``` http://127.0.0.1:8000/items/foo-item?needy=sooooneedy ``` ...this would work: ```JSON { "item_id": "foo-item", "needy": "sooooneedy" }
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 5.1K bytes - Viewed (0) -
docs/en/docs/tutorial/security/first-steps.md
* The frontend stores that token temporarily somewhere. * The user clicks in the frontend to go to another section of the frontend web app. * The frontend needs to fetch some more data from the API. * But it needs authentication for that specific endpoint. * So, to authenticate with our API, it sends a header `Authorization` with a value of `Bearer ` plus the token.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 9.2K bytes - Viewed (0) -
impl/maven-core/lifecycle-executor.txt
. . </plugins>
Registered: Sun Nov 03 03:35:11 UTC 2024 - Last Modified: Fri Oct 25 12:31:46 UTC 2024 - 9.7K bytes - Viewed (0) -
docs/en/docs/deployment/https.md
So, to renew the certificates, the renewal program needs to **prove** to the authority (Let's Encrypt) that it indeed **"owns" and controls that domain**. To do that, and to accommodate different application needs, there are several ways it can do it. Some popular ways are: * **Modify some DNS records**.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 12K bytes - Viewed (0) -
impl/maven-core/src/main/java/org/apache/maven/lifecycle/LifecycleExecutor.java
@Deprecated String ROLE = LifecycleExecutor.class.getName(); // For a given project packaging find all the plugins that are bound to any registered // lifecycles. The project builder needs to now what default plugin information needs to be // merged into POM being built. Once the POM builder has this plugin information, versions can be assigned
Registered: Sun Nov 03 03:35:11 UTC 2024 - Last Modified: Fri Oct 25 12:31:46 UTC 2024 - 4.2K bytes - Viewed (0) -
docs/en/docs/how-to/custom-docs-ui-assets.md
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Mon Oct 28 10:42:34 UTC 2024 - 7.3K bytes - Viewed (0)