<profile version="1.0">
      <inspection_tool class="BodyLimit" enabled="true" level="WARNING" enabled_by_default="true" />
      <inspection_tool class="GrazieCommit" enabled="true" level="TYPO" enabled_by_default="true" />
      <inspection_tool class="SubjectBodySeparation" enabled="true" level="ERROR" enabled_by_default="true" />
      <inspection_tool class="SubjectLimit" enabled="true" level="WARNING" enabled_by_default="true" />

    }

    public String getId() {
        return groupId + ":" + artifactId + ":" + version;
    }

          ]]></code>
        </codeSegment>
      </codeSegments>
    </class>

    <class xdoc.anchorName="mojo">
      <name>MojoDescriptor</name>
      <version>1.0.0+</version>
      <description>A Mojo description.</description>
      <fields>
        <field>
          <name>goal</name>

  </description>
  <defaults>
    <default>
      <key>package</key>
      <value>org.apache.maven.plugin.resources.remote</value>
    </default>
  </defaults>
  <classes>
    <class rootElement="true" xml.tagName="remoteResourcesBundle">
      <name>RemoteResourcesBundle</name>
      <version>1.1.0</version>
      <description>Root element of the remote-resources.xml file.</description>
      <fields>

          <sourcepath>doesnotexist</sourcepath>
          <!-- Note that we do need to build Javadoc for *some* class. Otherwise, we get an empty Javadoc jar, which the Sonatype repository manager rejects. To avoid that, we've introduced a dummy class. But we made it package-private so that no one can depend on it. That in turn forced us to configure Javadoc to show package-private APIs. -->
          <show>package</show>

						</data>
						<data>
							<type>files</type>
							<paths>
								<path>${project.build.directory}/fess/WEB-INF/classes/org/codelibs/fess/FessBoot.class</path>
								<path>${project.build.directory}/fess/WEB-INF/classes/org/codelibs/fess/FessBoot$FessBootPropsTranslator.class</path>
							</paths>
							<dst>${packaging.fess.lib.dir}/classes/org/codelibs/fess/</dst>
							<mapper>
								<type>perm</type>

          <association xml.itemsStyle="flat">
            <type>Lifecycle</type>
            <multiplicity>*</multiplicity>
          </association>
        </field>
      </fields>
    </class>
    <class>
      <name>Lifecycle</name>
      <version>1.0.0</version>
      <description>A custom lifecycle mapping definition.</description>
      <fields>
        <field>
          <name>id</name>

    </dependency>
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-toolchain-model</artifactId>
    </dependency>
    <!-- Used for Javadoc in a deprecated class only -->
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-toolchain-builder</artifactId>
    </dependency>
    <dependency>
      <groupId>org.apache.maven</groupId>

    <inspection_tool class="AsciiDocLinkResolve" enabled="false" level="ERROR" enabled_by_default="false" />
    <inspection_tool class="CatchMayIgnoreException" enabled="true" level="ERROR" enabled_by_default="true" />
    <inspection_tool class="Convert2streamapi" enabled="false" level="INFORMATION" enabled_by_default="false" />

          </association>
        </field>
      </fields>
    </class>
    <class>
      <name>PluginManagement</name>
      <version>4.0.0+</version>
      <superClass>PluginContainer</superClass>
      <description>Section for management of default plugin information for use in a group of POMs.
      </description>
    </class>
    <class>
      <name>Reporting</name>
      <version>4.0.0+</version>

    Extension descriptor, stored in <code>META-INF/maven/extension.xml</code> in an extension's jar artifact to
    precisely control parts of the extension and dependencies to expose in the API class loader.
    Maven uses Plexus Classworlds to build the class loader hierarchy, therefore some concepts used in this extensions
    stem from Plexus Classworlds originally.