</field>
        <field>
          <name>module</name>
          <version>4.1.0+</version>
          <description>
            <![CDATA[
            Name of the Java module (or other language-specific module) which is built by the sources.
            This element can be specified in a Maven project containing multiple Java modules.

        final int bodyFixed = 48; // body size minus 1 for structure size field overlap
        final int payloadStart = headerLen + bodyFixed;
        final int bodyLen = bodyFixed + inputCount + outputCount;

        byte[] buf = new byte[bodyLen];
        int pos = 0;

        // structureSize (LE) - includes 1 byte of the variable part
        SMBUtil.writeInt2(49, buf, pos);
        pos += 2;

  <groupId>com.example.group</groupId>
  <artifactId>testvalidpom</artifactId>
  <version>0.0.1-SNAPSHOT</version>

  <description>
    This will test if the module validator recognized that this dependency with classifier
    is not the same as the module itself.
  </description>
  <dependencies>
    <dependency>
      <groupId>com.example.group</groupId>
      <artifactId>testvalidpom</artifactId>

  <groupId>com.example.group</groupId>
  <artifactId>testinvalidpom</artifactId>
  <version>0.0.1-SNAPSHOT</version>

  <description>
    This will test if the module validator recognized that this
    dependency is the same as the module itself.
  </description>
  <dependencies>
    <dependency>
      <groupId>com.example.group</groupId>
      <artifactId>testinvalidpom</artifactId>

<module>
<source path="">
  <!-- Hack to keep collect from hiding collect.testing supersource: -->
  <exclude name="**/testing/**"/>
</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see

                        null,
                        true));

        // Verify that we get the same exception when the artifactId does not match the module name
        assertExceptionMessageContains("", "anotherArtifact");

        // Verify that no exception is thrown when the artifactId is the module name
        when(artifact.getArtifactId()).thenReturn("org.foo.bar");
        projectManager.attachArtifact(project, artifact, artifactPath);

        @Override
        public void afterProjectsRead(MavenSession session) {
            injectReactorDependency(session.getProjects(), "module-a", "module-b");
        }

        private void injectReactorDependency(List<MavenProject> projects, String moduleFrom, String moduleTo) {
            for (MavenProject project : projects) {

  <parent>
    <groupId>cyclic-reference</groupId>
    <artifactId>parent</artifactId>
    <version>1.0-SNAPSHOT</version>
  </parent>
  <artifactId>module-b</artifactId>

  <dependencies>
    <dependency>
      <groupId>cyclic-reference</groupId>
      <artifactId>module-a</artifactId>
      <version>1.0-SNAPSHOT</version>
    </dependency>
  </dependencies>

<module>
<source path="">
  <!-- Hack to keep collect from hiding collect.testing supersource: -->
  <exclude name="**/testing/**"/>
</source>

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see

			</plugin>
			<plugin>
				<artifactId>maven-jar-plugin</artifactId>
				<configuration>
					<archive>
						<manifestEntries>
							<Automatic-Module-Name>org.codelibs.fess.crawler.lasta</Automatic-Module-Name>
						</manifestEntries>
					</archive>
				</configuration>
			</plugin>
			<plugin>
				<groupId>com.mycila</groupId>
				<artifactId>license-maven-plugin</artifactId>