- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 91 for samp (0.16 sec)
-
maven-api-impl/src/main/java/org/apache/maven/internal/impl/resolver/RemoteSnapshotMetadataGenerator.java
* processes one artifact at a time and hence cannot associate the artifacts from the same project to use the * same timestamp+buildno for the snapshot versions. Allowing the caller to pass in metadata from a previous * deployment allows to re-establish the association between the artifacts of the same project. */ for (Metadata metadata : request.getMetadata()) {
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Apr 12 10:50:18 GMT 2024 - 4.3K bytes - Viewed (0) -
maven-core/src/site/apt/configuration-management.apt
the project level, and the user level. On the site level you can configure maven for all users utilizing the local installation, the group level allows configuration management for all the projects that belong to the same group, the project level allows configuration management at the project level, and the user level allows users to override settings on the site level, group level and project level. * Site configuration
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Mar 18 00:24:53 GMT 2024 - 5.8K bytes - Viewed (0) -
maven-api-impl/src/main/java/org/apache/maven/internal/impl/resolver/VersionsMetadataGenerator.java
* processes one artifact at a time and hence cannot associate the artifacts from the same project to use the * same version index. Allowing the caller to pass in metadata from a previous deployment allows to re-establish * the association between the artifacts of the same project. */ for (Iterator<? extends Metadata> it = metadatas.iterator(); it.hasNext(); ) {
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Apr 12 10:50:18 GMT 2024 - 3.9K bytes - Viewed (0) -
maven-api-impl/src/main/java/org/apache/maven/internal/impl/model/DefaultModelProcessor.java
* * This leads to a second side effect in that any @Inject request for just ModelProcessor in * the same injector is immediately matched to this explicit binding, which means extensions * cannot override this binding. This is because the lookup is always short-circuited in this * specific situation (plain @Inject request, and plain explicit binding for the same type.) * * The simplest solution is to use a custom @Named here so it isn't bound under the plain key.
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Apr 12 10:50:18 GMT 2024 - 5.8K bytes - Viewed (0) -
maven-core/src/site/apt/getting-to-container-configured-mojos.apt
--- Getting to Plexus-configured Mojos --- John Casey --- 2005-04-29 Abstract We're moving toward integrating mojos as first-class plexus components, while at the same time avoiding introducing required plexus dependencies into the mojo development model. In order to really achieve this, we need mojo configurations (which are
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jan 30 15:20:35 GMT 2023 - 4.1K bytes - Viewed (0) -
maven-api-impl/src/main/java/org/apache/maven/internal/impl/DefaultDependencyResolverResult.java
* For the test output directory, the rules are more complex and are governed by the fact that * Java does not accept the placement of two modules of the same name on the module-path. * 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:
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/test/resources-project-builder/unique-repo-id/plugin-repo/pom.xml
<artifactId>test</artifactId> <version>0.1</version> <packaging>jar</packaging> <name>Maven Integration Test :: MNG-4193</name> <description> Test that multiple plugin repository declarations with the same id cause a validation error. </description> <pluginRepositories> <pluginRepository> <id>one</id> <url>https://repo1.maven.org/maven2</url> </pluginRepository> <pluginRepository>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 1.4K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/merged-plugin-exec-order/w-plugin-mgmt/sub/pom.xml
<artifactId>parent</artifactId> <version>0.1</version> </parent> <artifactId>child</artifactId> <name>Maven Integration Test :: MNG-3925</name> <description> Test that plugin executions (in the same phase) are properly ordered after inheritance/merge with parent executions. </description> <build> <plugins> <plugin> <groupId>org.apache.maven.its.plugins</groupId>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 2.1K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/plugin-exec-order/w-plugin-mgmt/pom.xml
<artifactId>test</artifactId> <version>0.1</version> <packaging>pom</packaging> <name>Maven Integration Test :: MNG-3887</name> <description> Test that multiple plugin executions bound to the same phase are executed in the order given by the POM. </description> <build> <!-- This project uses plugin management for the test plugin --> <pluginManagement> <plugins> <plugin>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 2.3K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/DuplicateProjectException.java
*/ package org.apache.maven; import java.io.File; import java.util.LinkedHashMap; import java.util.List; import java.util.Map; /** * Signals a collision of two or more projects with the same g:a:v during a reactor build. * */ public class DuplicateProjectException extends MavenExecutionException { private Map<String, List<File>> collisions; /**
Java - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Wed Sep 06 08:39:32 GMT 2023 - 1.9K bytes - Viewed (0)