Maven报错：无法找到包中的符号类，新手Maven使用求助

Hey there! As someone new to Maven, this error is totally normal—let's break down why it's happening and how to fix it, plus walk through the key Maven rules you need to know here.

Why You're Seeing This Error #

Maven works on a "Convention Over Configuration" principle—it expects your code to live in specific directories by default. If your Callee class isn't in the right spot, Maven won't compile it, so when it tries to build Caller, it can't find the Callee symbol at all.

Let's start with the most common fix: getting your project structure right.

Step 1: Fix Your Project Directory Structure #

Maven requires production code to live under src/main/java—this is non-negotiable unless you explicitly reconfigure it (which you don't want to do as a beginner). Your project should look exactly like this:

your-maven-project/
├── pom.xml
└── src/
    └── main/
        └── java/
            └── maven/
                ├── callee/
                │   └── Callee.java
                └── caller/
                    └── Caller.java

Double-check that both your Callee.java and Caller.java are nested under src/main/java following their package paths (maven.callee and maven.caller respectively).

Step 2: Make Sure Your pom.xml Is Valid #

You need a basic pom.xml in your project root to tell Maven what kind of project this is. Here's a minimal working example:

<?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.yourname</groupId> <!-- Replace with your own group ID (e.g., your company/name) -->
    <artifactId>maven-basic-demo</artifactId> <!-- Your project name -->
    <version>1.0-SNAPSHOT</version>

    <properties>
        <maven.compiler.source>11</maven.compiler.source> <!-- Match your JDK version (8, 11, 17, etc.) -->
        <maven.compiler.target>11</maven.compiler.target>
    </properties>
</project>

Step 3: Compile and Run Correctly #

Open a terminal in your project root (the folder with pom.xml), then run these commands in order:

1. Clean and compile your code:

   mvn clean compile
   

   This command deletes old compiled files (in the target/ folder) and compiles all .java files under src/main/java. The compiled .class files will end up in target/classes/.

2. Run your Caller class:

   mvn exec:java -Dexec.mainClass="maven.caller.Caller"
   

   This tells Maven to execute the main method in maven.caller.Caller—it will automatically use the compiled classes from target/classes so Caller can find Callee.

Key Maven Mechanisms to Understand #

Let's tie this back to why this works, so you don't hit the same issue again:

• Convention Over Configuration: Maven's default directory structure removes the need to manually tell it where your code lives. src/main/java is for production code, src/test/java for tests—Maven scans these directories automatically.
• Classpath During Compilation: When Maven compiles Caller, it adds target/classes to the classpath. Since Callee is compiled into this folder, Caller can reference it without any extra setup. If Callee wasn't in src/main/java, it wouldn't be in target/classes, hence the "cannot find symbol" error.
• Maven Lifecycle: Commands like clean and compile are part of Maven's build lifecycle. clean resets your build environment, compile runs the compilation step—following this order ensures you're always working with fresh, compiled code.

Quick Verification #

After running mvn clean compile, check the target/classes folder—you should see:

target/classes/
└── maven/
    ├── callee/
    │   └── Callee.class
    └── caller/
        └── Caller.class

If both .class files exist, you're good to go—running the exec command will print Callee says: You called me! as expected.

内容的提问来源于stack exchange，提问作者DerMann