<artifactId>guava-testlib</artifactId>
      <version>${project.version}</version>
      <classifier>tests</classifier>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>com.google.guava</groupId>
      <artifactId>guava-tests</artifactId>
      <version>${project.version}</version>
      <classifier>tests</classifier>
      <scope>test</scope>
    </dependency>
    <dependency>

				<test.command.args>--illegal-access=permit</test.command.args>
			</properties>
		</profile>
		<profile>
			<id>integrationTests</id>
			<properties>
				<test.include.path>**/*Tests.java</test.include.path>
				<test.command.args />
			</properties>
		</profile>
	</profiles>
	<build>
		<finalName>fess</finalName>
		<resources>
			<resource>
				<directory>src/main/resources</directory>

      </activation>
      <properties>
        <!--
            Some tests need reflective access to the internals of these packages. It is only the
            tests themselves and not the code being tested that needs that access, though there's no
            obvious way to ensure that.

            We could consider arranging things so that only the tests we know need this would get