*/
    private PathModularization() {
        descriptors = Collections.emptyMap();
        isModuleHierarchy = false;
    }

    /**
     * Finds module information in the given JAR file, output directory, or test output directory.
     * If no module is found, or if module information cannot be extracted, then this constructor
     * builds an empty map.
     *

                } else {
                    logger.warn("Failed to interpolate missing file location for profile activator: " + fileString
                            + ", enable verbose output (-X) for more details");
                }
            }
        }

        return false;
    }

    public void enableLogging(Logger logger) {
        this.logger = logger;
    }

         * <p>
         * Note: if a reactor build contains a plugin (with issues) and later that built plugin is used in build,
         * it will be reported as "external". It is up to developer to correctly interpret output (GAV) of issues
         * and realize that in this case he wears two hats:" "user" and "(plugin) developer".
         */
        EXTERNAL
    }

    /**

     *           (a module existing only in test output, not in main output) should be uncommon.</li>
     *     </ul>
     *   </li>
     *   <li>Otherwise (test output contains no module information), then:
     *     <ul>
     *       <li>If the main output is on the module-path, place the test output
     *           on a {@code --patch-module} option.</li>

     * @param projectId The {@code <groupId>:<artifactId>:<version>} of the corresponding project, may be {@code null}
     *            to force output of model id and source.
     * @return The formatted problem location or an empty string if unknown, never {@code null}.
     */
    public static String formatLocation(ModelProblem problem, String projectId) {

    //      mojo descriptor which comes back. All the free form parsing needs to be done somewhere else, this is
    //      really the function of the CLI, and then the pre-processing of that output still needs to be fed into
    //      a hinting process which helps flesh out the full specification of the plugin. The plugin manager should

                        message = "Invalid POM for " + artifact.getId()
                                + ", transitive dependencies (if any) will not be available"
                                + ", enable verbose output (-X) for more details";
                    }

                    if (logger.isDebugEnabled()) {
                        message += ": " + e.getMessage();
                    }

/**
 * A factory for {@link MessageBuilder}.
 *
 * @since 4.0.0
 */
@Experimental
public interface MessageBuilderFactory extends Service {
    /**
     * Checks if the underlying output does support styling or not.
     * @return whether color styling is supported or not
     */
    boolean isColorEnabled();

    /**
     * Returns the terminal width or <code>-1</code> if not supported.

corresponding java.util.logging.Logger instance. LogKit from Apache's Avalon project. Each named Log instance is connected to a corresponding LogKit Logger. NoOpLog implementation that simply swallows all log output, for all named Log instances. SimpleLog implementation that writes all log output, for all named Log instances, to System.err. Quick Start Guide For those impatient to just get on with it, the following example illustrates the typical declaration and use of a logger that is named (by convention)...

public abstract void consumeLine(String); } org/codehaus/plexus/util/cli/StreamFeeder.class package org.codehaus.plexus.util.cli; public synchronized class StreamFeeder extends Thread { private java.io.InputStream input; private java.io.OutputStream output; private boolean done; public void StreamFeeder(java.io.InputStream, java.io.OutputStream); public void run(); public void close(); public boolean isDone(); private void feed() throws java.io.IOException; } org/codehaus/plexus/util/cli/StreamPumper.class...