首页 > 解决方案 > 如何使用 maven 定义和使用 ${project.basedir}?

问题描述

我试图更好地理解如何在 Maven 中解析相对路径。我在这里看到了“解析相对路径”。project.getBasedir()这是使用获取路径的好习惯。最初我以为我不必设置,所以我创建了一个 maven 项目创建了一个TestClass.java并测试了以下内容:

在 TestClass.java

System.out.println(project.getBaseDir());
System.out.println(project.getBaseDir()+"/folder1/folder2");

这给我带来了错误:无法解析符号“项目”。

  1. 所以我想我必须修改我的pom,但是如何修改我的pom呢?
  2. 另外,在 Maven 中连接路径的最佳实践是什么?如何改进project.getBaseDir()+"/folder1/folder2"呢?

下面是我的POM:

<?xml version="1.0" encoding="UTF-8"?>

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <groupId>com.moga</groupId>
  <artifactId>capacityplan</artifactId>
  <version>1.0-SNAPSHOT</version>

  <name>capacityplan</name>
  <!-- FIXME change it to the project's website -->
  <url>http://www.example.com</url>

  <properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <!-- <maven.compiler.source>1.7</maven.compiler.source> -->
    <!-- <maven.compiler.target>1.7</maven.compiler.target> -->
    <maven.compiler.release>15</maven.compiler.release>

  </properties>

  <dependencies>
<!--    TODO:Remove Junit4-->
    <dependency>
      <groupId>junit</groupId>
      <artifactId>junit</artifactId>
      <version>4.12</version>
      <scope>test</scope>
    </dependency>

    <dependency>
      <groupId>org.junit.jupiter</groupId>
      <artifactId>junit-jupiter-api</artifactId>
      <version>5.7.2</version>
      <scope>test</scope>
    </dependency>

    <!--        Start as per Junit5 Doc https://junit.org/junit5/docs/current/user-guide/#running-tests-build-maven-engines-configure-->
    <dependency>
      <groupId>org.junit.jupiter</groupId>
      <artifactId>junit-jupiter-engine</artifactId>
      <version>5.7.2</version>
      <scope>test</scope>
    </dependency>
    <!--        End -->

    <dependency>
      <groupId>org.junit.vintage</groupId>
      <artifactId>junit-vintage-engine</artifactId>
      <version>5.7.2</version>
      <scope>test</scope>
    </dependency>

    <dependency>
      <groupId>com.moga</groupId>
      <artifactId>genetic</artifactId>
      <version>1.0-SNAPSHOT</version>
    </dependency>
  </dependencies>

  <build>
<!--    <sourceDirectory>${basedir}/src/main/java</sourceDirectory>-->
<!--    <testSourceDirectory>${basedir}/src/test/java</testSourceDirectory>-->
<!--    <outputDirectory>${basedir}/target/classes</outputDirectory>-->
<!--    <testOutputDirectory>${basedir}/target/test-classes</testOutputDirectory>-->

    <pluginManagement><!-- lock down plugins versions to avoid using Maven defaults (may be moved to parent pom) -->
      <plugins>
        <!-- Define Main class, see https://www.baeldung.com/maven-java-main-method -->
        <plugin>
          <groupId>com.moga</groupId>
          <artifactId>capacityplan</artifactId>
          <version>1.0-SNAPSHOT</version>
          <configuration>
            <mainClass>com.moga.planning.nsga2.RunCapacityPlanning</mainClass>
          </configuration>
        </plugin>
        <!-- clean lifecycle, see https://maven.apache.org/ref/current/maven-core/lifecycles.html#clean_Lifecycle -->
        <plugin>
          <artifactId>maven-clean-plugin</artifactId>
          <version>3.1.0</version>
        </plugin>
        <!-- default lifecycle, jar packaging: see https://maven.apache.org/ref/current/maven-core/default-bindings.html#Plugin_bindings_for_jar_packaging -->
        <plugin>
          <artifactId>maven-resources-plugin</artifactId>
          <version>3.0.2</version>
        </plugin>
        <plugin>
          <artifactId>maven-compiler-plugin</artifactId>
          <version>3.8.0</version>
        </plugin>
        <plugin>
          <artifactId>maven-surefire-plugin</artifactId>
          <version>2.22.1</version>
        </plugin>

        <!--        As per Junit5 Doc https://junit.org/junit5/docs/current/user-guide/#running-tests-build-maven-engines-configure-->
        <plugin>
          <artifactId>maven-failsafe-plugin</artifactId>
          <version>2.22.2</version>
        </plugin>
        <!--        End Junit5-->

        <plugin>
          <artifactId>maven-jar-plugin</artifactId>
          <version>3.0.2</version>
        </plugin>
        <plugin>
          <artifactId>maven-install-plugin</artifactId>
          <version>2.5.2</version>
        </plugin>
        <plugin>
          <artifactId>maven-deploy-plugin</artifactId>
          <version>2.8.2</version>
        </plugin>
        <!-- site lifecycle, see https://maven.apache.org/ref/current/maven-core/lifecycles.html#site_Lifecycle -->
        <plugin>
          <artifactId>maven-site-plugin</artifactId>
          <version>3.7.1</version>
        </plugin>
        <plugin>
          <artifactId>maven-project-info-reports-plugin</artifactId>
          <version>3.0.0</version>
        </plugin>
      </plugins>
    </pluginManagement>
  </build>
</project>

标签: javamavenpath

解决方案


推荐阅读