util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see https://goo.gl/pRV3Yn for details.

    The summary is that it ignores one file in favor of the other.
    util.concurrent, like nearly all our packages, has two .gwt.xml files: one
    for prod and one for tests. However, unlike our other packages, as of this

    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see https://goo.gl/pRV3Yn for details.

    The summary is that it ignores one file in favor of the other.
    util.concurrent, like nearly all our packages, has two .gwt.xml files: one
    for prod and one for tests. However, unlike our other packages, as of this

    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see https://goo.gl/pRV3Yn for details.

    The summary is that it ignores one file in favor of the other.
    util.concurrent, like nearly all our packages, has two .gwt.xml files: one
    for prod and one for tests. However, unlike our other packages, as of this

    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see https://goo.gl/pRV3Yn for details.

    The summary is that it ignores one file in favor of the other.
    util.concurrent, like nearly all our packages, has two .gwt.xml files: one
    for prod and one for tests. However, unlike our other packages, as of this

    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see https://goo.gl/pRV3Yn for details.

    The summary is that it ignores one file in favor of the other.
    util.concurrent, like nearly all our packages, has two .gwt.xml files: one
    for prod and one for tests. However, unlike our other packages, as of this

								<group>${packaging.fess.group}</group>
							</mapper>
						</data>
						<!-- Add configuration files -->
						<data>
							<type>files</type>
							<paths>
								<path>${project.basedir}/src/main/assemblies/files/tomcat_config.properties</path>
								<path>${project.basedir}/src/main/assemblies/files/logging.properties</path>
							</paths>
							<dst>${packaging.fess.conf.dir}</dst>
							<mapper>

            packages, like RangeTest. The reason for this is that GWT doesn't distinguish between
            .java files in c.g.c.collect.Collect, a module that the c.g.c.base test module inherits,
            and .java files in c.g.c.collect.testModule, one that it doesn't[*]. Consequently,
            c.g.c.base.testModule transitively pulls in .java files from both modules while reading

      <outputDirectory>conf</outputDirectory>
    </fileSet>
    <fileSet>
      <directory>src/assembly/maven/lib</directory>
      <outputDirectory>lib</outputDirectory>
    </fileSet>
  </fileSets>

  <files>
    <file>
      <sources>
        <source>src/assembly/shared/validate.cmd</source>
        <source>src/assembly/shared/mvnvalidate.cmd</source>
        <source>src/assembly/shared/init.cmd</source>

    <suppress checks="JavadocPackage"
              files=".*[/\\]process-services[/\\]src[/\\]main[/\\]java[/\\]org[/\\]gradle[/\\]process[/\\][^/\\]+"/>
    <suppress checks="JavadocPackage"
              files=".*[/\\]plugins[/\\]src[/\\]main[/\\]java[/\\]org[/\\]gradle[/\\]jvm[/\\][^/\\]+"/>
    <suppress checks="JavadocPackage"

    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see https://goo.gl/pRV3Yn for details.

    The summary is that it ignores one file in favor of the other.
    util.concurrent, like nearly all our packages, has two .gwt.xml files: one
    for prod and one for tests. However, unlike our other packages, as of this