<version>4.0.0-beta-1-SNAPSHOT</version>
  </parent>

  <artifactId>maven-api</artifactId>
  <packaging>pom</packaging>
  <name>Maven 4 API</name>
  <description>A new immutable API for Maven 4 to better manage what plugins and extensions can influence.</description>

  <modules>
    <module>maven-api-meta</module>
    <module>maven-api-di</module>
    <module>maven-api-xml</module>
    <module>maven-api-model</module>

            path. As the name suggests, this is similar to requiresDependencyResolution and supports the same values.
            The important difference is this will not resolve the files for the dependencies, i.e. the artifacts
            associated with a Maven project can lack a file. As such, this annotation is meant for Mojos that only

      <fields>
        <field>
          <name>remoteResources</name>
          <version>1.1.0</version>
          <description>
            Remote resources that are contained in a remote resources bundle.
          </description>
          <association>
            <type>String</type>
            <multiplicity>*</multiplicity>
          </association>
        </field>

              <option value="$PROJECT_DIR$/js/js.translator/testData/out/codegen/wasmBox/$TEST_DATA_FILE$.wat" />
            </array>
          </value>
        </entry>
        <entry key="$PROJECT_DIR$/compiler/testData/codegen/boxInline">
          <value>
            <array>

    <!--
      | We may potentially want to export these, but right now I'm not sure that anything Guice specific needs
      | 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.

   | it to several places.
   |
   | That repository definition will have a unique id, so we can create a mirror reference for that
   | repository, to be used as an alternate download site. The mirror site will be the preferred
   | server for that repository.
   |-->
  <mirrors>
    <!-- mirror
     | Specifies a repository mirror site to use instead of a given repository. The repository that

            is then described by additional elements.
            Projects should only list the license(s) that applies to the project
            and not the licenses that apply to dependencies.
            If multiple licenses are listed, it is assumed that the user can select
            any of them, not that they must accept all.
            ]]>
          </description>
          <association>

          <type>String</type>
          <description>What the last version added to the directory is, including both releases and snapshots ("groupId/artifactId" directory only)</description>
        </field>
        <field>
          <name>release</name>
          <version>1.0.0+</version>
          <type>String</type>

	<artifactId>jcifs</artifactId>
	<version>2.1.38-SNAPSHOT</version>
	<packaging>jar</packaging>
	<name>jCIFS</name>
	<url>https://github.com/codelibs/jcifs</url>
	<description>JCIFS is an Open Source client library that implements the CIFS/SMB networking protocol in 100% Java</description>
	<licenses>
		<license>
			<name>GNU Lesser General Public License, version 2.1</name>
			<url>http://www.gnu.org/licenses/old-licenses/lgpl-2.1.txt</url>

              <!-- END default constructor on Plexus/JSR 330 components -->
              <!-- system property with that name no longer evaluated -->
              <exclude>org.apache.maven.project.DefaultProjectBuilder#DISABLE_GLOBAL_MODEL_CACHE_SYSTEM_PROPERTY</exclude>