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

 * limitations under the License.
 */

package model

import com.fasterxml.jackson.databind.ObjectMapper
import com.fasterxml.jackson.module.kotlin.readValue
import com.fasterxml.jackson.module.kotlin.registerKotlinModule
import java.io.File

val ignoredSubprojects =
    listOf(
        "soak", // soak test
        "distributions-integ-tests", // build distribution testing

  <name>Model urls inheritance test parent</name>
  <description>MNG-5951 MNG-6059 child.x.y.inherit.append.path="false" for each url to avoid automatic path addition when inheriting</description>

  <modules>
    <module>../inheritance</module>
  </modules>

  <!-- 5 urls in the pom to configure for not adding path -->
  <url>http://www.apache.org/path/to/parent/</url>
  <scm child.scm.connection.inherit.append.path="false"

      description: |
        Requesting we remove a module here only hides the generated documentation on pkg.go.dev.
        It does not affect the behaviour of proxy.golang.org or the go command.
        Instead we recommend using the retract directive which will be processed by all 3 of the above.

        If you have deleted your repo, please recreate it and publish a retraction.

      - name: Check links
        uses: lycheeverse/lychee-action@v2.7.0
        with:
          # excluded:
          # - notes.md and notes-templates.md - because they are a part of user guide
          # - Kotlin's Module.md - because it's a part of the Kotlin DSL docs
          args: >
            --no-progress --offline '**/*.md' --include-fragments
            --exclude-path 'platforms/documentation/docs/src/docs/release/notes.md'

## Composition by architecture modules

Each [architecture module and platform](platforms.md) can contribute code to any of the runtimes.
Not every module contributes to every runtime.

The core-runtime module defines each runtime:

- The target JVM for the runtime. Each runtime has its own JVM compatibility constraints.

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

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

                                                                name="deleteAllWords"
                                                                data-toggle="modal" data-target="#confirmToAllDelete"
                                                                value="<la:message key="labels.design_delete_button" />">

                }
            });

            t.transform(project, systemSessionMock, Sources.buildSource(beforePomFile), tempFile);
        }
        Diff diff = DiffBuilder.compare(afterPomFile.toFile())
                .withTest(tempFile.toFile())
                .ignoreComments()
                .ignoreWhitespace()
                .build();
        assertFalse(diff.hasDifferences(), "XML files should be identical: " + diff.toString());
    }

module github.com/minio/minio/docs/debugging/pprofgoparser

go 1.21