<type>String</type>
          <description>
            Flags this Mojo as requiring information about the dependencies that would make up the specified class
            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

	<property name="webinf.dir" value="${basedir}/src/main/webapp/WEB-INF" />
	<property name="crawler.dir" value="${basedir}/src/main/webapp/WEB-INF/env/crawler" />
	<property name="suggest.dir" value="${basedir}/src/main/webapp/WEB-INF/env/suggest" />
	<property name="thumbnail.dir" value="${basedir}/src/main/webapp/WEB-INF/env/thumbnail" />
	<property name="site.dir" value="${basedir}/src/main/webapp/WEB-INF/site" />

			<artifactId>bcmail-jdk18on</artifactId>
			<version>${bouncycastle.version}</version>
		</dependency>

		<!-- suggest library -->
		<dependency>
			<groupId>org.codelibs.fess</groupId>
			<artifactId>fess-suggest</artifactId>
			<version>${suggest.version}</version>
		</dependency>

		<!-- fileupload -->
		<dependency>
			<groupId>commons-fileupload</groupId>

          <!-- TODO(cpovirk): Move this to the parent after making the package-list files available there. -->
          <!-- We add the link ourselves, both so that we can choose Java 9 over the version that -source suggests and so that we can solve the JSR305 problem described below. -->
          <detectJavaApiLink>false</detectJavaApiLink>
          <offlineLinks>

          <!-- TODO(cpovirk): Move this to the parent after making the package-list files available there. -->
          <!-- We add the link ourselves, both so that we can choose Java 9 over the version that -source suggests and so that we can solve the JSR305 problem described below. -->
          <detectJavaApiLink>false</detectJavaApiLink>
          <offlineLinks>