Hey there! Let's troubleshoot that annoying "Unknown lifecycle phase" error you're hitting when trying to launch your Spring Boot project with the local profile. I’ve dealt with this exact issue before, so here are the most reliable fixes to try step by step:

1. Fix Your Command Syntax First (Most Common Culprit!) #

The #1 reason for this error is misplacing the JVM system property in your command. Maven requires all -D parameters to come before the plugin goal (spring-boot:run), otherwise it’ll misinterpret the property as an unrecognized lifecycle phase.

Wrong Command: #

mvn spring-boot:run -Dspring-boot.run.profiles=local

Correct Command: #

mvn -Dspring-boot.run.profiles=local spring-boot:run

Notice how we moved -Dspring-boot.run.profiles=local to the front? That tells Maven this is a system property, not a phase to execute.

2. Verify Spring Boot Maven Plugin Setup #

If the command syntax checks out, make sure your pom.xml has the Spring Boot Maven plugin properly configured, with a version matching your Spring Boot 2.2.5 release:

<build>
    <plugins>
        <plugin>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-maven-plugin</artifactId>
            <version>2.2.5.RELEASE</version>
            <executions>
                <execution>
                    <goals>
                        <goal>repackage</goal>
                    </goals>
                </execution>
            </executions>
        </plugin>
    </plugins>
</build>

Without this plugin or with a mismatched version, Maven won’t recognize the spring-boot:run goal at all.

3. Confirm Maven & Java Environment Compatibility #

Your stack (Spring Boot 2.2.5 + Maven 3.6.3 + Java 11) is officially compatible, but let’s double-check your environment:
Run this command to verify your Maven and Java versions:

mvn -v

Ensure the output shows Java 11 as the runtime and Maven 3.6.3. If not, check your JAVA_HOME and PATH environment variables to make sure they point to the correct JDK 11 installation.

4. Validate Your Local Profile Exists #

Make sure you actually have an application-local.properties (or .yml) file in your src/main/resources directory with valid local configuration. For example:

# application-local.properties
server.port=8081
database.url=jdbc:mysql://localhost:3306/local_db
# Add other local-specific settings here

If the file is missing or in the wrong location, even a correct command might lead to unexpected issues.

5. Try Alternative Profile Activation Methods #

If the above steps don’t work, experiment with other ways to activate the local profile:

• Use Maven Profiles in pom.xml: Add this section to your pom.xml, then run mvn spring-boot:run -Plocal (note the uppercase -P):

  <profiles>
      <profile>
          <id>local</id>
          <properties>
              <spring.profiles.active>local</spring.profiles.active>
          </properties>
      </profile>
  </profiles>
  

• IDE VM Options: If you’re using an IDE like IntelliJ or Eclipse, add -Dspring.profiles.active=local to your run configuration’s VM options, then launch the project directly from the IDE.

6. Clean Maven Cache #

Sometimes corrupted cached dependencies cause weird behavior. Try clearing the cache and rebuilding:

mvn clean install -DskipTests
mvn -Dspring-boot.run.profiles=local spring-boot:run

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