v4.0.7

Changed

• Updated dependencies

v4.0.6

Fixed

• Previously, when the working directory contains a Git repository without any commits, heroku-jvm-application-deployer crashed with a NullPointerException. This case is now handled gracefully. (#319)

Changed

• Updated dependencies

v4.0.5

Added

• Upload progress reporting (#313)

v4.0.4

• Updated dependencies

v4.0.3

• Updated dependencies

v4.0.2

Prepare release v4.0.2 (#282)

Co-authored-by: heroku-linguist[bot] <136119646+heroku-linguist[bot]@users.noreply.github.com>

v4.0.1

Changed

• Specifying a main JAR or WAR file is no longer required. This allows easy deployment in cases where application startup is managed by a shell script, such as when using sbt-native-packager. (#258)

Removed

• Workaround for JDK-8220723 that affected older (2019) OpenJDK versions. (#260)

v4.0.0

This project used to contain both a Maven Plugin and a CLI tool for deploying Java applications to Heroku without using Git.

Starting with this version, it no longer contains the Maven Plugin. Users are expected to migrate to the improved command line tool (formerly known as heroku-deploy-standalone). Previously, the Maven plugin and CLI supported different features and were maintained at different levels. This release unifies everything into a new CLI. This allows customers to use the same tool for a variety of JVM languages, independent of their build tool of choice.

See the README for a brief overview or refer to the --help output of the CLI for usage info.

Historic changelog entries are preserved below for completeness. But be aware that this release substantially changed the
nature of this project.

Changed

• Use correct Heroku-Deploy-Type header when deploying. (#247)
• Update release process to add the JAR file to GitHub releases. (#240)
• Add proper CLI to configure all aspects of app deployment. Previously used Java properties are no longer supported. See --help for usage. (#232)
• Unify usage between WAR and JAR files. heroku-jvm-application-deployer will now automatically use the correct mode based on file extension. (#232)
• Default webapp-runner version is now always the most recently released version. (#232)

v3.0.7

Changed

• Update dependencies.