- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 16 for have (0.15 sec)
-
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 Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jul 18 17:22:19 GMT 2022 - 9.7K 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 Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jul 18 22:45:13 GMT 2022 - 12.9K 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/src/site/apt/plugin-execution-isolation.apt
ClassWorlds ClassRealm that is populated with the JAR containing the component in question and all of its dependencies. Using ClassWorlds notation for realms we have the following: +-----+ [plexus.core] ^ | [plexus.core.maven] ^ ^ | | [plugin0] [plugin1] +-----+
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Fri Feb 03 09:12:28 GMT 2017 - 2.3K bytes - Viewed (0) -
apache-maven/src/main/appended-resources/licenses/Apache-2.0.txt
this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Tue Jan 28 11:47:17 GMT 2020 - 11.1K bytes - Viewed (0) -
.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 Apr 28 03:35:10 GMT 2024 - Last Modified: Tue Dec 20 13:14:27 GMT 2022 - 1.9K bytes - Viewed (0) -
maven-core/src/test/resources/org/apache/maven/extension/test-extension-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 Mar 31 03:35:09 GMT 2024 - Last Modified: Sat Nov 09 12:45:14 GMT 2019 - 9.8K bytes - Viewed (0) -
apache-maven/src/main/appended-resources/licenses/EPL-1.0.txt
related to Product X, those performance claims and warranties are such Commercial Contributor's responsibility alone. Under this section, the Commercial Contributor would have to defend claims against the other Contributors related to those performance claims and warranties, and if a court requires any other Contributor to pay any damages as a result, the Commercial Contributor must pay those damages.
Plain Text - Registered: Sun Apr 28 03:35:10 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
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 Apr 28 03:35:10 GMT 2024 - Last Modified: Sat Sep 10 19:27:25 GMT 2022 - 5.5K bytes - Viewed (0)