<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>maven-t06</groupId>
  <artifactId>p0</artifactId>
  <packaging>pom</packaging>
  <name>p0</name>
  <version>1.0</version>
  <organization>
    <name>Codehaus</name>
  </organization>
  <dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>maven-test</groupId>
        <artifactId>t06-a</artifactId>
        <version>1.0</version>
      </dependency>

import org.apache.maven.plugin.version.PluginVersionResolutionException;
import org.apache.maven.project.MavenProject;

/**
 * @since 3.0
 */
public interface LifecycleExecutionPlanCalculator {
    MavenExecutionPlan calculateExecutionPlan(MavenSession session, MavenProject project, List<Task> tasks)
            throws PluginNotFoundException, PluginResolutionException, LifecyclePhaseNotFoundException,

		<developerConnection>scm:git:******@****.***:codelibs/curl4j.git</developerConnection>
		<url>******@****.***:codelibs/curl4j.git</url>
	  <tag>HEAD</tag>
  </scm>
	<properties>
		<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
	</properties>
	<build>
		<plugins>
			<plugin>
				<artifactId>maven-compiler-plugin</artifactId>
				<version>3.14.0</version>
				<configuration>

# Generate the API docs
./gradlew dokkaHtmlMultiModule

mv ./build/dokka/htmlMultiModule docs/4.x

# Copy in special files that GitHub wants in the project root.
cat README.md | grep -v 'project website' > docs/index.md
cp CHANGELOG.md docs/changelogs/changelog.md
cp CONTRIBUTING.md docs/contribute/contributing.md

# Build the site locally

Most of these ideas would be more or less **independent**, and in most cases you should only need to study them if they apply directly to **your project**.

If something seems interesting and useful to your project, go ahead and check it, but otherwise, you might probably just skip them.

/// tip

            <configuration>
              <outputDirectory>${project.build.directory}/jar-sisu</outputDirectory>
              <resources>
                <resource>
                  <directory>${project.build.outputDirectory}</directory>
                </resource>
                <resource>
                  <directory>${project.build.testOutputDirectory}</directory>
                  <includes>

     */
    @Nonnull
    Instant getStartTime();

    /**
     * Gets the directory of the topmost project being built, usually the current directory or the
     * directory pointed at by the {@code -f/--file} command line argument.
     *
     * @return the directory of the topmost project, never {@code null}
     * @see Project#isTopProject()
     * @see #getRootDirectory()
     */
    @Nonnull
    Path getTopDirectory();

    }

    public static RepositoryRequest getRepositoryRequest(MavenSession session, MavenProject project) {
        RepositoryRequest request = new DefaultRepositoryRequest();

        request.setLocalRepository(session.getLocalRepository());
        if (project != null) {
            request.setRemoteRepositories(project.getPluginArtifactRepositories());
        }
        request.setOffline(session.isOffline());

	</build>
	<dependencies>
		<dependency>
			<groupId>org.codelibs.fess</groupId>
			<artifactId>fess-crawler</artifactId>
			<version>${project.version}</version>
		</dependency>
		<dependency>
			<groupId>org.codelibs.fess</groupId>
			<artifactId>fess-crawler-lasta</artifactId>
			<version>${project.version}</version>
			<optional>true</optional>
		</dependency>
		<dependency>
			<groupId>org.codelibs</groupId>

     * consumer project.
     * <p>
     * Note: This property is about "build path", whatever it means in the scope of the consumer project. It is NOT
     * about Java classpath or anything alike. How artifact is being consumed depends heavily on the consumer project.
     * Resolver is and will remain agnostic of consumer project use cases.
     */