<modelVersion>4.0.0</modelVersion>
  <parent>
    <groupId>org.sonatype.mavenbook.multi</groupId>
    <artifactId>simple-parent</artifactId>
  </parent>

  <artifactId>simple-webapp</artifactId>
  <name>Multi Chapter Simple Web Application Project</name>
  <dependencies>
    <dependency>
      <groupId>org.sonatype.mavenbook.multi</groupId>
      <artifactId>simple-weather</artifactId>
    </dependency>
  </dependencies>
  <build>

         * to new fixed version, or by dropping plugin use from currently built project.
         * <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

                session.getRepositorySession());
        assertNotNull(mojoDescriptor);
        assertEquals(goal, mojoDescriptor.getGoal());
        // igorf: plugin realm comes later
        // assertNotNull( mojoDescriptor.getRealm() );

        PluginDescriptor pluginDescriptor = mojoDescriptor.getPluginDescriptor();
        assertNotNull(pluginDescriptor);

            /*
             * Module hierarchy: many modules, one per directory, with descriptor at the root of the sub-directory.
             * This is the layout of output directories in projects using the new (Java 9 and later) way to organize
             * source files.
             */
            if (Files.isDirectory(file)) {
                Map<Path, String> names = new HashMap<>();

      | to be made available to plugin authors. If we find people are getting fancy and want to take advantage of
      | Guice specifics we can expose that later. Really some testing needs to be done to see full hiding
      | of Guice has any impact on what we may categorize as a standard JSR-330 based Tesla/Maven plugin.

        <exportedPackage>com.google.inject.*</exportedPackage>

METHOD org.hamcrest Interface Description All Known Implementing Classes: BaseDescription, Description.NullDescription, StringDescription public interface Description A description of a Matcher. A Matcher will describe itself to a description which can later be used for reporting. See Also: SelfDescribing.describeTo(Description) Nested Class Summary static class Description.NullDescription Field Summary static Description NONE A description that consumes input but does nothing. Method Summary Description...

/**
 * Component for use by the <code>maven-toolchains-plugin</code> only.
 * It provides API: <ol>
 * <li>to retrieve every toolchains available in user settings,</li>
 * <li>to store chosen toolchain into build context for later use by toolchain-aware plugins.</li>
 * </ol>
 *
 * @since 2.0.9
 * @see ToolchainManager#getToolchainFromBuildContext(String, MavenSession)
 */
public interface ToolchainManagerPrivate {

    /**

  <parent>
    <groupId>org.sonatype.mavenbook.multi</groupId>
    <artifactId>parent</artifactId>
  </parent>
  <artifactId>simple-parent</artifactId>
  <packaging>pom</packaging>
  <name>Multi Chapter Simple Parent Project</name>

  <modules>
    <module>simple-weather</module>
    <module>simple-webapp</module>

    <!-- On purpose at the end, project graph is responsible for ordering -->

logging in server-based applications that can be used around a variety of different logging implementations, including prebuilt support for the following: Log4J (version 1.2 or later) from Apache's Jakarta project. Each named Log instance is connected to a corresponding Log4J Logger. JDK Logging API, included in JDK 1.4 or later systems. Each named Log instance is connected to a corresponding java.util.logging.Logger instance. LogKit from Apache's Avalon project. Each named Log instance is connected...

                     * happens, add on class-path or module-path if allowed, or keep patching otherwise.
                     * The latter case (keep patching) is okay if the main module will be defined later.
                     */
                    type = cache.selectPathType(pathTypes, filter, path).orElse(type);
                }
                addPathElement(type, info.getKey());