Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 10 for pulling (0.16 sec)

  1. maven-builder-support/src/main/java/org/apache/maven/building/ProblemCollector.java

         */
        void add(Problem.Severity severity, String message, int line, int column, Exception cause);
    
        /**
         * The next messages will be bound to this source. When calling this method again, previous messages keep
         * their source, but the next messages will use the new source.
         *
         * @param source a source
         */
        void setSource(String source);
    
        /**
         *
    Java
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Wed Sep 06 08:39:32 GMT 2023
    - 1.9K bytes
    - Viewed (0)
  2. api/maven-api-xml/src/main/java/org/apache/maven/api/xml/XmlNode.java

        /**
         * This default mode for combining children DOMs during merge means that where element names match, the process will
         * try to merge the element data, rather than putting the dominant and recessive elements (which share the same
         * element name) as siblings in the resulting DOM.
         */
        String DEFAULT_CHILDREN_COMBINATION_MODE = CHILDREN_COMBINATION_MERGE;
    
    Java
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Mon Nov 27 23:11:34 GMT 2023
    - 4.3K bytes
    - Viewed (0)
  3. .github/workflows/maven.yml

                  target_branch=$branch
                  target_user=$user
                else
                  echo "Could not find fork \"$user/$repo\" or a branch \"$branch\" in this fork. Falling back to \"$target_branch\" in \"$target_user/$repo\"."
                fi
              else
                echo "Integration tests will run against $target_user/$repo for master builds."
              fi
    Others
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Sun Mar 03 21:28:30 GMT 2024
    - 4.5K bytes
    - Viewed (0)
  4. maven-compat/src/main/java/org/apache/maven/repository/legacy/resolver/DefaultLegacyArtifactCollector.java

            // explicit child override depMgmt (viz. depMgmt should only
            // provide defaults to children, but should override transitives).
            // We can do this by calling isChildOfRootNode on the current node.
            if ((artifact.getVersion() != null)
                    && (!node.isChildOfRootNode() || node.getArtifact().getVersion() == null)) {
    Java
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Wed Sep 06 11:28:54 GMT 2023
    - 36.7K bytes
    - Viewed (0)
  5. api/maven-api-core/src/main/java/org/apache/maven/api/services/ModelProblemCollector.java

    /**
     * Collects problems that are encountered during model building. The primary purpose of this component is to account for
     * the fact that the problem reporter has/should not have information about the calling context and hence cannot provide
     * an expressive source hint for the model problem. Instead, the source hint is configured by the model builder before
    Java
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Fri Apr 12 10:50:18 GMT 2024
    - 2.5K bytes
    - Viewed (0)
  6. maven-compat/src/main/java/org/apache/maven/artifact/resolver/DefaultArtifactResolver.java

            // We have metadata retrieval problems, or there are cycles that have been detected
            // so we give this back to the calling code and let them deal with this information
            // appropriately.
    
            if (result.hasMetadataResolutionExceptions()
                    || result.hasVersionRangeViolations()
    Java
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Thu Apr 25 05:46:50 GMT 2024
    - 24.8K bytes
    - Viewed (0)
  7. maven-api-impl/src/main/java/org/apache/maven/internal/impl/model/DefaultModelProblemCollector.java

    /**
     * Collects problems that are encountered during model building. The primary purpose of this component is to account for
     * the fact that the problem reporter has/should not have information about the calling context and hence cannot provide
     * an expressive source hint for the model problem. Instead, the source hint is configured by the model builder before
    Java
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Fri Apr 12 10:50:18 GMT 2024
    - 6.3K bytes
    - Viewed (0)
  8. maven-core/src/test/resources/apiv4-repo/commons-logging/commons-logging/1.0.3/commons-logging-1.0.3.jar

    Acquire a reference to an instance of org.apache.commons.logging.Log, by calling the factory method LogFactory.getInstance(String name). Your application can contain references to multiple loggers that are used for different purposes. A typical scenario for a server application is to have each major component of the server use its own Log instance. Cause messages to be logged (if the corresponding detail level is enabled) by calling appropriate methods (debug(), info(), warn(), error, and fatal()). For...
    Archive
    - Registered: Sun Apr 28 03:35:10 GMT 2024
    - Last Modified: Tue Dec 19 19:08:55 GMT 2023
    - 30.9K bytes
    - Viewed (0)
  9. api/maven-api-core/src/main/java/org/apache/maven/api/plugin/Log.java

     * convenience, to enable developers to pass things like <code>java.lang.StringBuffer</code> directly into the logger,
     * rather than formatting first by calling <code>toString()</code>.
     *
     * @since 4.0.0
     */
    @Experimental
    @Provider
    public interface Log {
        /**
         * @return true if the <b>debug</b> error level is enabled
         */
        boolean isDebugEnabled();
    Java
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Wed Feb 28 23:54:53 GMT 2024
    - 5.1K bytes
    - Viewed (0)
  10. maven-core/src/test/resources/apiv4-repo/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar

    Acquire a reference to an instance of org.apache.commons.logging.Log, by calling the factory method LogFactory.getInstance(String name). Your application can contain references to multiple loggers that are used for different purposes. A typical scenario for a server application is to have each major component of the server use its own Log instance. Cause messages to be logged (if the corresponding detail level is enabled) by calling appropriate methods (trace(), debug(), info(), warn(), error, and fatal())....
    Archive
    - Registered: Sun Apr 28 03:35:10 GMT 2024
    - Last Modified: Tue Dec 19 19:08:55 GMT 2023
    - 37.1K bytes
    - Viewed (0)
Back to top