Heroku部署规则变更咨询：Java Web应用是否必须包含pom.xml？

Great question! Let me break down the changes to Heroku's Java deployment workflow and why that pom.xml file is now mandatory, even for dependency-free web apps.

The Core Reason for the Change #

Heroku updated its Java buildpack in late 2017 to standardize how Java web apps are built and run. Before this shift, the buildpack had more flexible (but inconsistent) ways to detect and run unmanaged web projects. Now, it relies on Maven (or Gradle) as the primary tool to:

• Identify your project as a Java web application
• Automatically fetch and configure Web App Runner—an embedded Tomcat container that Heroku uses to execute your WAR file
• Generate consistent startup scripts and ensure environment parity across deployments

Without a pom.xml (or build.gradle for Gradle projects), the buildpack can't confirm your project is Java-based, nor can it handle the necessary setup to run your app on Heroku's infrastructure.

Pre-September 2017: The Old Workflow #

Before the update, Heroku supported deploying "raw" dynamic web projects—think a directory with just WEB-INF and your static files—without any build tool configuration. The buildpack would automatically detect the WEB-INF folder, spin up a basic container, and run the app.

While this was convenient for simple apps, it had major drawbacks:

• No control over the container version (Tomcat, Jetty, etc.)
• No way to manage additional dependencies if you later needed them
• Inconsistent behavior across different app setups, leading to hard-to-debug deployment issues

How to Handle Dependency-Free Apps Today #

If your app truly doesn't need dependency management, you don't have to write a complex pom.xml. A minimal, skeleton file is all you need to satisfy the buildpack. Here's an 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.yourdomain</groupId>
    <artifactId>your-app-name</artifactId>
    <version>1.0-SNAPSHOT</version>
    <packaging>war</packaging>

    <!-- Only required dependency: Web App Runner for running the WAR -->
    <dependencies>
        <dependency>
            <groupId>com.heroku</groupId>
            <artifactId>webapp-runner</artifactId>
            <version>9.0.70.1</version>
            <scope>provided</scope>
        </dependency>
    </dependencies>

    <build>
        <plugins>
            <!-- Configure Maven to package your existing web files into a WAR -->
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-war-plugin</artifactId>
                <version>3.3.2</version>
                <configuration>
                    <!-- Point to your existing web content directory -->
                    <webResources>
                        <resource>
                            <directory>./</directory>
                            <includes>
                                <include>WEB-INF/**</include>
                                <include>index.html</include>
                                <!-- Add any other static files you need -->
                            </includes>
                        </resource>
                    </webResources>
                </configuration>
            </plugin>
        </plugins>
    </build>
</project>

This file tells Heroku:

1. This is a WAR-packaged Java web app
2. It needs Web App Runner to run
3. Where to find your existing web content (adjust the <directory> and <includes> if your files are in a different location)

Wrap-Up #

The shift to requiring build tool configuration was all about reliability and consistency. While it adds a small upfront step, it ensures your app runs in a predictable environment, and gives you the flexibility to add dependencies or customize your deployment later on.

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