Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for nofollow (2.17 sec)

  1. apache-maven/src/assembly/maven/lib/jansi-native/README.txt

    This directory contains Jansi native libraries extracted from Jansi JAR.
    
    You can add your own build for platforms not natively supported by Jansi.
    See here [1] on how to compile for your platform and here [2] how libraries
    follow Jansi's directory and filename conventions.
    
    [1] https://github.com/fusesource/jansi/tree/master/src/main/native
    Plain Text
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Mon Jul 18 17:22:19 GMT 2022
    - 486 bytes
    - Viewed (0)
  2. maven-core/src/main/java/org/apache/maven/AbstractMavenLifecycleParticipant.java

     */
    package org.apache.maven;
    
    import org.apache.maven.execution.MavenSession;
    
    /**
     * Allows core extensions to participate in Maven build session lifecycle.
     *
     * All callback methods (will) follow beforeXXX/afterXXX naming pattern to
     * indicate at what lifecycle point it is being called.
     *
     * @see <a href="https://maven.apache.org/examples/maven-3-lifecycle-extensions.html">example</a>
    Java
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Tue Nov 22 13:26:01 GMT 2022
    - 2.9K bytes
    - Viewed (0)
  3. maven-core/plugin-manager.txt

     * application data - do we need a dictionary for our applications like Apple does. We could easily
     * hook into this and this is the model we need to follow - how many of our REST services do not map
     * directory to a method in the application interface?
     *
     * - research extension points versus plugins
     *
    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)
Back to top