Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 2 of 2 for provider (0.12 sec)

  1. 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)
  2. 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