<excludes>
              <!-- The root module (where applicable) is withheld because it is provided at `META-INF/versions/9/`. -->
              <exclude>/module-info.class</exclude>
              <!-- Avoid duplicating compiled classes within the `META-INF/versions/9/` root. -->
              <exclude>META-INF/versions/9/com/**/*.class</exclude>
            </excludes>
            <archive>
              <manifestEntries>

            <excludes>
              <!-- The root module (where applicable) is withheld because it is provided at `META-INF/versions/9/`. -->
              <exclude>/module-info.class</exclude>
              <!-- Avoid duplicating compiled classes within the `META-INF/versions/9/` root. -->
              <exclude>META-INF/versions/9/com/**/*.class</exclude>
            </excludes>
            <archive>
              <manifestEntries>

  <id>extension</id>
  <name>ExtensionDescriptor</name>
  <description><![CDATA[
    Extension descriptor, stored in <code>META-INF/maven/extension.xml</code> in an extension's jar artifact to
    precisely control parts of the extension and dependencies to expose in the API class loader.

 * @deprecated since 4.0.0, use {@code maven-api-impl} jar instead
 */
@Deprecated(since = "4.0.0")
class PluginsMetadataGenerator implements MetadataGenerator {
    private static final String PLUGIN_DESCRIPTOR_LOCATION = "META-INF/maven/plugin.xml";

    private final Logger logger = LoggerFactory.getLogger(getClass());

    private final Map<Object, PluginsMetadata> processedPlugins;

    private final Date timestamp;

@Deprecated
public class ExpressionDocumenter {

    private static final String[] EXPRESSION_ROOTS = {"project", "settings", "session", "plugin", "rootless"};

    private static final String EXPRESSION_DOCO_ROOTPATH = "META-INF/maven/plugin-expressions/";

    private static Map<String, Expression> expressionDocumentation;

    public static Map<String, Expression> load() throws ExpressionDocumentationException {

                </resource>
                <resource>
                  <directory>${project.build.testOutputDirectory}</directory>
                  <includes>
                    <include>META-INF/sisu/**</include>
                  </includes>
                </resource>
              </resources>
            </configuration>
          </execution>
        </executions>
      </plugin>
      <plugin>

            }
            String path;
            if ("view".equals(jspType)) {
                path = "/WEB-INF/" + jspType + values[0] + "/" + jspFileName;
            } else {
                path = "/WEB-INF/" + jspType + "/" + jspFileName;
            }
            final File jspFile = new File(getServletContext().getRealPath(path));
            if (!jspFile.exists()) {

 * base for all providers that register such extensions.
 * <p>
 * Implementations of this interface are discovered through the Java ServiceLoader mechanism.
 * Each implementation must be registered in a {@code META-INF/services/} file corresponding
 * to the specific provider interface being implemented.
 * <p>
 * Example implementation for a custom language provider:
 * <pre>

  </dependencySets>
  <fileSets>
    <fileSet>
      <includes>
        <include>README*</include>
      </includes>
    </fileSet>
    <fileSet>
      <directory>target/maven-shared-archive-resources/META-INF</directory>
      <outputDirectory>./</outputDirectory>
      <includes>
        <include>LICENSE</include>
        <include>NOTICE</include>
      </includes>
    </fileSet>
    <fileSet>

 {{{./apidocs/org/apache/maven/cli/logging/Slf4jConfigurationFactory.html}Slf4jConfigurationFactory}} /
 {{{./apidocs/org/apache/maven/cli/logging/Slf4jConfiguration.html}Slf4jConfiguration}}.

~~ TODO document META-INF/maven/slf4j-configuration.properties

* Getting Logger Instance

 Starting with Maven 3.1.0, SLF4J Logger can be used directly. This technique can be used safely in Maven core