- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 37 for What (0.15 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) -
.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/site/apt/offline-mode.apt
* Otherwise, don't bind the mojo. Log a debug message to indicate that it is sensitive the online state of the application, and that this state is currently wrong for execution. <<NOTE:>> Do we want to fail when we cannot bind a mojo to the lifecycle because of offline/online status? That would probably indicate that the user was trying to do something they cannot succeed at for now...so we probably
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Mar 18 00:24:53 GMT 2024 - 10.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) -
apache-maven/src/main/appended-resources/licenses/unrecognized-javax.annotation-api-1.3.2.txt
Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Tue May 11 18:59:18 GMT 2021 - 38.5K bytes - Viewed (0) -
apache-maven/README.txt
Apache Maven What is it? ----------- Maven is a software project management and comprehension tool. Based on the concept of a Project Object Model (POM), Maven can manage a project's build, reporting and documentation from a central piece of information. Documentation ------------- The most up-to-date documentation can be found at https://maven.apache.org/. Release Notes -------------
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Sat Mar 13 20:21:20 GMT 2021 - 2.5K bytes - Viewed (0) -
maven-core/plugin-manager.txt
* * h3. plugins should be able to have specific metadata for a plugin model and that be translated - * dependencies - resources - configuration - extension points of plugins * * For a particular application plugin there will be a declarative descriptor for that plugin type. * * - nexus - the plugin class - UI to contribute - what JS to hook into the UI - what resources to
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Mon Jul 18 22:45:13 GMT 2022 - 12.9K bytes - Viewed (0) -
maven-core/lifecycle-executor.txt
. . . </plugins> We need this form so that the model builder can make the first pass at merging. Full merging cannot be done because we don't know what the version of the plugin is yet that the user has requested. For plugins in the default lifecycle they are typically defined in the plugin management section of the parent POM. When the merging is complete we are going to have something that looks like the following: <plugins> <plugin>
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Mon Jul 18 17:22:19 GMT 2022 - 9.7K bytes - Viewed (0) -
apache-maven/src/main/appended-resources/licenses/EPL-1.0.txt
including direct, indirect, special, incidental and consequential damages, such as lost profits; iii) states that any provisions which differ from this Agreement are offered by that Contributor alone and not by any other party; and iv) states that source code for the Program is available from such Contributor, and informs licensees how to obtain it in a reasonable manner on or through
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Mon Sep 17 05:50:12 GMT 2018 - 11.1K bytes - Viewed (0) -
apache-maven/src/main/appended-resources/META-INF/NOTICE.vm
being redistributed by another party ("Redistributor") and different terms and conditions may apply to your use of any object code in the Content. Check the Redistributor's license that was provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise indicated below, the terms and conditions of the EPL still apply to any source code in the Content
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Sat Sep 10 19:27:25 GMT 2022 - 5.5K bytes - Viewed (0)