<param name="plugin.name" value="minhash" />
			<param name="plugin.version" value="3.5.0" />
			<param name="plugin.zip.version" value="3.5.0" />
		</antcall>

		<antcall target="remove.jars" />
	</target>

	<target name="install.plugin">
		<get dest="${target.dir}">

			<param name="module.version" value="${opensearch.version}" />
			<param name="module.zip.version" value="${opensearch.version}" />
		</antcall>

		<antcall target="remove.jars" />
	</target>

	<target name="install.module">
		<get dest="${target.dir}">

		<delete>
			<fileset dir="${webinf.dir}/plugin">
				<include name="**/*.jar" />
			</fileset>
		</delete>
	</target>

	<target name="install.env.jar">
		<get dest="${target.dir}">
			<url url="${repo.url}/${jar.groupId}/${jar.artifactId}/${jar.version}/${jar.artifactId}-${file.version}.jar" />
		</get>
		<copy file="${target.dir}/${jar.artifactId}-${file.version}.jar" todir="${crawler.dir}/lib" />

default.

Another example is the `discovery-gce` plugin. It is *vital* to folks running
in [GCP](https://cloud.google.com/) but useless otherwise and it depends on a
dozen extra jars.

#### `qa`
Honestly this is kind of in flux and we're not 100% sure where we'll end up.
Right now the directory contains
* Tests that require multiple modules or plugins to work

    shouldn’t do it. But if that’s how you want to live your life we won’t stand
    in your way!


## Version 3.0.1

_2016-01-14_

 *  Rollback OSGi support. This was causing library jars to include more classes
    than expected, which interfered with Gradle builds.


## Version 3.0.0

_2016-01-13_

This release commits to a stable 3.0 API. Read the 3.0.0-RC1 changes for advice

            Some examples are {@code jar}, {@code war}, {@code ejb-client}
            and {@code test-jar}: see <a href="../maven-core/artifact-handlers.html">default
            artifact handlers</a> for a list. New types can be defined by extensions, so this is not a complete list.
            ]]>
          </description>
          <type>String</type>
          <defaultValue>jar</defaultValue>
        </field>

						</ant>
						<ant antfile="${basedir}/plugin.xml" target="install.plugins">
							<property name="with.fess" value="true" />
						</ant>
						<ant antfile="deps.xml" target="install.jars" />
						<echo message="fess.version=${project.version}" file="${basedir}/src/main/webapp/WEB-INF/project.properties" />
					</target>
				</configuration>
				<goals>
					<goal>run</goal>
				</goals>

    /**
     * Artifact type name for a JAR file that can be placed either on the class path or on the module path.
     * The path (classes or modules) is chosen by the plugin, possibly using heuristic rules.
     * This is the behavior of Maven 3.
     */
    String JAR = "jar";

    /**
     * Artifact type name for a fat-JAR file that can be only on the class path.

META-INF/MANIFEST.MF Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Built-By: BEBE Build-Jdk: 1.6.0_07 META-INF/maven/org.apache.maven.its/a/pom.xml 4.0.0 org.apache.maven.its a 0.1 jar Maven Integration Test :: Dummy Artifact maven-core-it file:///${basedir}/repo META-INF/maven/org.apache.maven.its/a/pom.properties #Generated by Maven #Sat Oct 24 00:27:56 CEST 2009 version=0.1 groupId=org.apache.maven.its artifactId=a...

        File libDir = new File(tempDir, "lib");
        assertTrue(libDir.mkdir());

        // Create test jar files
        File jar1 = new File(libDir, "test1.jar");
        File jar2 = new File(libDir, "test2.JAR");
        File notJar = new File(libDir, "test.txt");
        assertTrue(jar1.createNewFile());
        assertTrue(jar2.createNewFile());
        assertTrue(notJar.createNewFile());