Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for provider (0.08 sec)

  1. apache-maven/src/main/appended-resources/licenses/CDDL+GPLv2-with-classpath-exception.txt

    header the words "Oracle designates this particular file as subject to
    the "Classpath" exception as provided by Oracle in the LICENSE file
    that accompanied this code."
    
    You should also note that Oracle includes multiple, independent
    programs in this software package. Some of those programs are provided
    under licenses deemed incompatible with the GPLv2 by the Free Software
    Registered: Sun Nov 03 03:35:11 UTC 2024
    - Last Modified: Fri May 17 19:14:22 UTC 2024
    - 38.5K bytes
    - Viewed (0)
  2. apache-maven/src/main/appended-resources/licenses/EPL-2.0.txt

    Eclipse Public License - v 2.0
    
        THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE
        PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION
        OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.
    
    1. DEFINITIONS
    
    "Contribution" means:
    
      a) in the case of the initial Contributor, the initial content
         Distributed under this Agreement, and
    
      b) in the case of each subsequent Contributor:
    Registered: Sun Nov 03 03:35:11 UTC 2024
    - Last Modified: Tue Jun 04 06:45:16 UTC 2024
    - 13.9K bytes
    - Viewed (0)
  3. compat/maven-model-builder/src/site/apt/index.apt

        encoding was used by plugins)
    
        * <<<$\{project.reporting.outputEncoding\}>>> for
        {{{https://cwiki.apache.org/confluence/display/MAVENOLD/Reporting+Encoding+Configuration}reporting output files encoding}}
        (defaults to <<<UTF-8>>> since Maven 4.0.0, no default value was provided in Maven 3.x, plugins usually defaulting
        to <<<UTF-8>>>)
    Registered: Sun Nov 03 03:35:11 UTC 2024
    - Last Modified: Fri Oct 25 12:31:46 UTC 2024
    - 13.2K bytes
    - Viewed (0)
  4. impl/maven-core/plugin-manager.txt

    but a resource needs to simply become the mapping mechanism by which parameters are taken from the REST side of the application and mapped into a method call within a given Plexus component. Whether that be the core Nexus application or a component provided by a plugin.
    
    At the very least in the short term the resource needs to know how to look up the component that is required to perform the work. This needs to be made simple, for the time being we can write and test plugins working in the...
    Registered: Sun Nov 03 03:35:11 UTC 2024
    - Last Modified: Fri Oct 25 12:31:46 UTC 2024
    - 12.9K bytes
    - Viewed (0)
Back to top