- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 322 for mplacer (0.18 sec)
-
api/maven-api-core/src/main/java/org/apache/maven/api/services/DependencyResolverResult.java
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Mar 01 17:18:13 GMT 2024 - 3.4K bytes - Viewed (0) -
api/maven-api-core/src/main/java/org/apache/maven/api/Type.java
/** * Artifact type name for a JAR file containing test classes. If the main artifact is placed on the class-path * ({@value #JAR} or {@value #CLASSPATH_JAR} types), then the test artifact will also be placed on the class-path. * Otherwise, if the main artifact is placed on the module-path ({@value #JAR} or {@value #MODULAR_JAR} types),
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Mar 29 09:32:19 GMT 2024 - 5.6K bytes - Viewed (0) -
maven-api-impl/src/main/java/org/apache/maven/internal/impl/DefaultDependencyResolverResult.java
* So the modular test output directory usually needs to be placed in a {@code --path-module} option. * * <ul> * <li>If the test output directory is modular, then: * <ul> * <li>If a test module name is identical to a main module name, * place the test directory in a {@code --patch-module} option.</li> * <li>Otherwise, place the test directory on the module-path. However, this case
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Mar 25 10:50:01 GMT 2024 - 14.2K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/internal/impl/PathModularizationCache.java
* * @param types types of path where a dependency can be placed * @param filter filter the paths accepted by the tool which will consume the path * @param path path to the JAR file or output directory of the dependency * @return where to place the dependency, or an empty value if the placement cannot be determined
Java - Registered: Sun Mar 24 03:35:10 GMT 2024 - Last Modified: Fri Mar 01 17:18:13 GMT 2024 - 5.2K bytes - Viewed (0) -
docs/en/docs/advanced/additional-responses.md
The correct place is: * In the key `content`, that has as value another JSON object (`dict`) that contains: * A key with the media type, e.g. `application/json`, that contains as value another JSON object, that contains: * A key `schema`, that has as the value the JSON Schema from the model, here's the correct place.
Plain Text - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Thu Jan 11 16:31:18 GMT 2024 - 8.8K bytes - Viewed (0) -
maven-api-impl/src/main/java/org/apache/maven/internal/impl/PathModularizationCache.java
* * @param types types of path where a dependency can be placed * @param filter filter the paths accepted by the tool which will consume the path * @param path path to the JAR file or output directory of the dependency * @return where to place the dependency, or an empty value if the placement cannot be determined
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Mar 25 10:50:01 GMT 2024 - 5.2K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/internal/impl/DefaultDependencyResolverResult.java
* So the modular test output directory usually needs to be placed in a {@code --path-module} option. * * <ul> * <li>If the test output directory is modular, then: * <ul> * <li>If a test module name is identical to a main module name, * place the test directory in a {@code --patch-module} option.</li> * <li>Otherwise, place the test directory on the module-path. However, this case
Java - Registered: Sun Mar 24 03:35:10 GMT 2024 - Last Modified: Fri Mar 01 17:18:13 GMT 2024 - 14.2K bytes - Viewed (0) -
api/maven-api-core/src/main/java/org/apache/maven/api/JavaPathType.java
* <p><b>Context-sensitive interpretation:</b> * A dependency with this path type will not necessarily be placed on the class-path. * There are two circumstances where the dependency may nevertheless be placed somewhere else: * </p> * <ul> * <li>If {@link #MODULES} path type is also set, then the dependency can be placed either on the * class-path or on the module-path, but only one of those. The choice is up to the plugin,
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Mar 01 17:18:13 GMT 2024 - 11.6K bytes - Viewed (0) -
android/guava/src/com/google/common/cache/Striped64.java
* overkill for most Atomics because they are usually irregularly * scattered in memory and thus don't interfere much with each * other. But Atomic objects residing in arrays will tend to be * placed adjacent to each other, and so will most often share * cache lines (with a huge negative performance impact) without * this precaution. * * In part because Cells are relatively large, we avoid creating
Java - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Thu Feb 22 17:40:56 GMT 2024 - 11.5K bytes - Viewed (0) -
api/maven-api-core/src/main/java/org/apache/maven/api/PathType.java
* * @see org.apache.maven.api.services.DependencyResolverResult#getDispatchedPaths() * * @since 4.0.0 */ @Experimental public interface PathType { /** * The type for all paths that could not be placed in any of the types requested by a caller. * This type can appear in the return value of a call to * {@link Session#resolveDependencies resolveDependencies(...)} when at least one dependency
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Mar 01 17:18:13 GMT 2024 - 4.9K bytes - Viewed (0)