- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 480 for What (0.13 sec)
-
maven-core/src/site/apt/inheritance.apt
- [artifactId] tells maven what the artifact name is for this particular project. Each project should have a distinct artifactId. - [version] tells maven what release of this artifact we're trying to produce. The fact that a project has a distinct pom.xml should indicate a separate release cycle that is also distinct to that project, so a concrete version declaration is required.
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jul 18 17:22:19 GMT 2022 - 3.5K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/lifecycle/LifecycleExecutor.java
// can be passed back so that the default configuration information can be populated. // // We need to know the specific version so that we can look up the right version of the plugin descriptor // which tells us what the default configuration is. // /**
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Wed Sep 06 08:39:32 GMT 2023 - 4.2K bytes - Viewed (0) -
maven-compat/src/main/mdo/paramdoc.mdo
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Fri Aug 21 15:04:07 GMT 2009 - 5.4K bytes - Viewed (0) -
.github/pull_request_template.md
Best practice is to use the JIRA issue title in both the pull request title and in the first line of the commit message. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Tue Dec 20 13:14:27 GMT 2022 - 1.9K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/lifecycle/MavenExecutionPlan.java
// 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 /** * MavenExecutionPlan */
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Wed Jan 10 12:55:54 GMT 2024 - 6.2K bytes - Viewed (0) -
maven-core/src/main/java/org/apache/maven/lifecycle/DefaultLifecycles.java
public Lifecycle get(String phase) { return getPhaseToLifecycleMap().get(phase); } /** * We use this to map all phases to the lifecycle that contains it. This is used so that a user can specify the * phase they want to execute and we can easily determine what lifecycle we need to run. * * @return A map of lifecycles, indexed on id */ public Map<String, Lifecycle> getPhaseToLifecycleMap() {
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Fri Apr 12 10:50:18 GMT 2024 - 6K bytes - Viewed (0) -
maven-core/src/site/apt/configuration-management.apt
maven 1.x and 2.x is that all project parameterization occurs in the POM and not from properties files. For many of the more advanced features in Maven2 it is critical that POMs be available in the local repository. Features like transitive dependencies and the new parent specification mechanism. The problem we run into is
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-core/src/main/java/org/apache/maven/execution/MavenSession.java
* Adapt a {@link MavenExecutionRequest} to a {@link Settings} object for use in the Maven core. * We want to make sure that what is ask for in the execution request overrides what is in the settings. * The CLI feeds into an execution request so if a particular value is present in the execution request * then we will take that over the value coming from the user settings. */
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Mon Mar 25 10:50:01 GMT 2024 - 16.6K bytes - Viewed (0) -
api/maven-api-core/src/main/java/org/apache/maven/api/PathScope.java
import org.apache.maven.api.annotations.Nonnull; import static org.apache.maven.api.ExtensibleEnums.pathScope; /** * Path scope. * A path scope is used to determine the kind of build or class path that will be built when resolving * dependencies using the {@link org.apache.maven.api.services.DependencyResolver} service. * <p> * This extensible enum has four defined values, {@link #MAIN_COMPILE}, {@link #MAIN_RUNTIME},
Java - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Fri Apr 12 10:50:18 GMT 2024 - 2.9K bytes - Viewed (0) -
api/pom.xml
<version>4.0.0-beta-1-SNAPSHOT</version> </parent> <artifactId>maven-api</artifactId> <packaging>pom</packaging> <name>Maven 4 API</name> <description>A new immutable API for Maven 4 to better manage what plugins and extensions can influence.</description> <modules> <module>maven-api-meta</module> <module>maven-api-di</module> <module>maven-api-xml</module> <module>maven-api-model</module>
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Thu Apr 25 08:48:58 GMT 2024 - 3.7K bytes - Viewed (0)