- Sort Score
- Result 10 results
- Languages All
Results 1 - 9 of 9 for have (0.13 sec)
-
.github/pull_request_template.md
require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[MNG-XXX] SUMMARY`, where you replace `MNG-XXX` and `SUMMARY` with the appropriate JIRA issue.
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/inheritance.apt
maven occur, the maven inheritance model must be pinned against a particular modelVersion. This is required so that a change from modelVersion 4.0.0 to 4.1.0 doesn't cause compatibility problems with users who have not upgraded their projects. It also allows for a certain amount of legacy support into the future. Therefore, we should rename this file from pom.xml in the maven-core
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) -
apache-maven/src/main/appended-resources/META-INF/NOTICE.vm
and such source code may be obtained at <a href="http://www.eclipse.org/">http://www.eclipse.org</a>.</p> <h3>Third Party Content</h3> <p>The Content includes items that have been sourced from third parties as set out below. If you did not receive this Content directly from the Eclipse Foundation, the following is provided for informational purposes only, and you should look
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) -
maven-core/src/site/apt/offline-mode.apt
operations to fail, then trying to help users decipher the error messages they get as a result. * Implications for Resolution ** Dependency Resolution This one is obvious...we only have access to the repositories using the file:// protocol and living on a truly local filesystem when offline. ** Plugin Resolution This is similar to dependency resolution. Plugin repositories not
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) -
README.md
the concept of a project object model (POM), Maven can manage a project's build, reporting and documentation from a central piece of information. If you think you have found a bug, please file an issue in the [Maven Issue Tracker][jira]. Documentation ------------- More information can be found on [Apache Maven Homepage][maven-home].
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Sun Mar 03 21:28:30 GMT 2024 - 4.3K bytes - Viewed (0) -
maven-core/src/site/apt/configuration-management.apt
that currently we have information about a project scattered across the project.xml and the various properties files. What needs to be done is to encapsulate all of this in the POM. Typically users parameterize the use of plugins, or have custom values like ${user.name} for use in elements like the <developerConnection/>. It would be idea if we
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/lifecycle-executor.txt
We have a lifecycle mapping for the packaging of *jar* below. You see that for this packaging we have a *default* lifecycle and a list of phases where each phase is a comma separated list of goals to run and they are in the form groupId:artifactId:version. <configuration> <lifecycles> <lifecycle> <id>default</id> <phases> <process-resources>org.apache.maven.plugins:maven-resources-plugin:resources</process-resources>
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) -
maven-core/src/test/resources/apiv4-repo/org/apache/maven/maven-parent/4/maven-parent-4.pom
<distributionManagement> <site> <id>apache.website</id> <url>scp://people.apache.org/www/maven.apache.org</url> </site> </distributionManagement> <!-- Disabled until projects have been made to comply <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-pmd-plugin</artifactId> <executions> <execution>
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Oct 02 08:41:25 GMT 2022 - 9.8K bytes - Viewed (0) -
maven-core/plugin-manager.txt
* Maven test harness for plugin execution model * Eclipse IDE tooling for plugin execution model and metadata model - we also seem to have information like the plugin lifecycle model that's buried inside the maven execution model - we also seem to have artifact information tangled inside the plugin model - we have to deal with scripting implementations (groovy, beanshell, ruby) - we need to deal with a shared context for plugins, like the guarded mojos
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)