Spring Boot应用部署失败求助：Maven仓库配置缺失

Looks like you ran into a common confusion between Maven's deploy goal and actually deploying your Spring Boot app to Heroku or running it locally. Let's break down the problem and fix it step by step.

Why the Error Happens #

The error message clearly points out the core issue:

Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project portfolio_app: Deployment failed: repository element was not specified in the POM inside distributionManagement element or in -DaltDeploymentRepository=id::layout::url parameter

Maven's deploy command is designed to push your built JAR artifact to a remote Maven repository (like Nexus, Artifactory, or Maven Central)—not to deploy your app to a cloud platform like Heroku or run it locally. Your current pom.xml doesn’t have the distributionManagement section configured, which tells Maven where to send the artifact during the deploy process. That’s exactly why the build fails.

How to Fix This #

1. Stop Using mvn deploy for Heroku/Local Runs #

You don’t need the mvn deploy command at all for these scenarios:

• Local testing: Run your app directly with:

  mvn spring-boot:run
  

  Or build the JAR first and execute it:

  mvn package
  java -jar target/portfolio_app-1.0-SNAPSHOT.jar
  

• Heroku deployment: Use either of these methods (your pom.xml already has the Heroku Maven plugin, so both work):
  • Git-based deployment (recommended):

    # Log into Heroku CLI first if you haven't
    heroku login
    # Create a Heroku app if you don't have one yet
    heroku create
    # Commit your latest changes
    git add .
    git commit -m "Prepare for Heroku deployment"
    # Push to Heroku's remote repository
    git push heroku main
    

  • Heroku Maven plugin:

    mvn heroku:deploy
    

2. If You Actually Need to Deploy to a Maven Repository #

If your goal was to push your JAR to a remote Maven repo (not Heroku), add the distributionManagement section to your pom.xml:

<project>
  <!-- ... existing content ... -->

  <distributionManagement>
    <!-- For stable release versions -->
    <repository>
      <id>your-release-repo-id</id>
      <url>https://your-repo-url/releases</url>
    </repository>
    <!-- For snapshot versions (like your 1.0-SNAPSHOT) -->
    <snapshotRepository>
      <id>your-snapshot-repo-id</id>
      <url>https://your-repo-url/snapshots</url>
    </snapshotRepository>
  </distributionManagement>

  <!-- ... existing content ... -->
</project>

You’ll also need to add repository credentials in your settings.xml (usually located at ~/.m2/settings.xml on Linux/macOS or C:\Users\your-user\.m2\settings.xml on Windows):

<settings>
  <servers>
    <server>
      <id>your-release-repo-id</id>
      <username>your-repo-username</username>
      <password>your-repo-password</password>
    </server>
    <server>
      <id>your-snapshot-repo-id</id>
      <username>your-repo-username</username>
      <password>your-repo-password</password>
    </server>
  </servers>
</settings>

Alternatively, you can pass repository details via command line temporarily:

mvn deploy -DaltDeploymentRepository=my-repo::default::https://your-repo-url/snapshots

Why Your Previous Similar App Worked #

Chances are, your earlier app never used the mvn deploy command—you probably used mvn spring-boot:run locally and git push heroku main or mvn heroku:deploy for Heroku. Neither of these require the distributionManagement config, which is why you never hit this error before.

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