</value>
      </option>
    </JavaCodeStyleSettings>
    <JetCodeStyleSettings>
      <option name="LINE_BREAK_AFTER_MULTILINE_WHEN_ENTRY" value="false" />
      <option name="ALLOW_TRAILING_COMMA" value="true" />
      <option name="CODE_STYLE_DEFAULTS" value="KOTLIN_OFFICIAL" />
    </JetCodeStyleSettings>
    <MarkdownNavigatorCodeStyleSettings>
      <option name="RIGHT_MARGIN" value="72" />

  <groupId>maven.t02</groupId>
  <artifactId>p2</artifactId>
  <packaging>pom</packaging>
  <name>p2</name>
  <version>1.0</version>
  <mailingLists>
    <mailingList>
      <name>mailing-list</name>
    </mailingList>
  </mailingLists>

  <groupId>org.apache.maven.its.mng3843.child</groupId>
  <artifactId>child-2</artifactId>
  <version>0.2</version>
  <packaging>jar</packaging>

  <mailingLists>
    <mailingList>
      <name>child-mailing-list</name>
    </mailingList>
  </mailingLists>

      <timezone>+1</timezone>
      <properties>
        <contributor>yes</contributor>
      </properties>
    </contributor>
  </contributors>

  <mailingLists>
    <mailingList>
      <name>project-mailing-list</name>
      <subscribe>subscribe@</subscribe>
      <unsubscribe>unsubscribe@</unsubscribe>
      <post>post@</post>
      <archive>mail-archive</archive>
      <otherArchives>

    buffer size (usually 4 or 8 KB). The text block is designed such that its length is exactly 32 KB after leading
    and trailing whitespace has been removed and all line terminators have been removed.
    -->
    <prop2>
00 KB     1         2         3         4         5         6  X
0         1         2         3         4         5         6  X

      <timezone>+1</timezone>
      <properties>
        <contributor>yes</contributor>
      </properties>
    </contributor>
  </contributors>

  <mailingLists>
    <mailingList>
      <name>project-mailing-list</name>
      <subscribe>subscribe@</subscribe>
      <unsubscribe>unsubscribe@</unsubscribe>
      <post>post@</post>
      <archive>mail-archive</archive>
      <otherArchives>

          </association>
        </field>
      </fields>
      <comment>We could probably have a specific element for a dev mailing list for things like CI,
        and maybe even a specific element for the user and scm mailing lists. Then leave the more
        lose structure for any other type of mailing list.</comment>
      <codeSegments>
        <codeSegment>
          <version>4.0.0+</version>
          <code>

    </developer>
  </developers>
  <contributors>
    <contributor>
      <name>parent-contributor</name>
    </contributor>
  </contributors>

  <mailingLists>
    <mailingList>
      <name>parent-mailing-list</name>
    </mailingList>
  </mailingLists>

  <prerequisites>
    <maven>2.0</maven>
  </prerequisites>

  <modules>
    <module>child-1</module>
    <module>child-2</module>
  </modules>

    <modelVersion>4.0.0</modelVersion>

    <parent>
        <groupId>org.apache.maven.its</groupId>
        <artifactId>parent</artifactId>
        <version>0.1</version>
    </parent>

    <artifactId>location-tracking</artifactId>
    <packaging>jar</packaging>

    <repositories>
        <repository>
            <id>remote-repo</id>
            <url>file://${basedir}/../../src/test/remote-repo</url>
        </repository>

			<arg>"fess_config.boost_document_rule/boost_document_rule"</arg>
		</postConstruct>
		<postConstruct name="addIndexConfig">
			<arg>"fess_config.crawling_info/crawling_info"</arg>
		</postConstruct>
		<postConstruct name="addIndexConfig">
			<arg>"fess_config.crawling_info_param/crawling_info_param"</arg>
		</postConstruct>
		<postConstruct name="addIndexConfig">
			<arg>"fess_config.data_config/data_config"</arg>
		</postConstruct>