- Sort Score
- Result 10 results
- Languages All
Results 1 - 6 of 6 for Feross (0.18 sec)
-
apache-maven/src/main/appended-resources/licenses/EPL-1.0.txt
such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable. If Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations of the Program with other software or hardware) infringes such Recipient's patent(s), then such Recipient's rights granted under Section
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) -
maven-core/src/site/apt/inheritance.apt
the top of that lineage to provide default values. The super model is where we place all the values which we believe to be standard, values that can be shared and utilized across all your Maven projects. +-----+ m0 <- m1 <- m2 +-----+ which is transformed into +-----+ super model <- m0 <- m1 <- m2 +-----+ +-----+ <project> <modelVersion>4.0.0</modelVersion>
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) -
LICENSE
Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Wed Sep 11 20:39:30 GMT 2013 - 11.1K bytes - Viewed (0) -
maven-core/src/site/apt/configuration-management.apt
Features like transitive dependencies and the new parent specification mechanism. The problem we run into is 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}
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/Apache-2.0.txt
Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Tue Jan 28 11:47:17 GMT 2020 - 11.1K bytes - Viewed (0) -
maven-core/plugin-manager.txt
h3. Plugins need a specific metadata model Each application will have its own model for plugins. Much of this model will be common across applications but there will always be issues specific to a particular applications’s plugins. Some of the issues that need to be taken into consideration: * Plugin dependencies * Plugin resources like JavaScript files or images
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)