All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
4.0.8 - 2025-01-07
- When the target app is using Fir, a default
project.toml
will now be generated and deployed alongside the app. This ensures that OpenJDK will be installed andProcfile
works as expected without the need for explicit configuration. (#369)
4.0.7 - 2024-07-17
- Updated dependencies
4.0.6 - 2024-05-07
- Previously, when the working directory contains a Git repository without any commits,
heroku-jvm-application-deployer
crashed with aNullPointerException
. This case is now handled gracefully. (#319)
- Updated dependencies
4.0.5 - 2024-05-06
- Upload progress reporting (#313)
4.0.4 - 2024-04-03
- Updated dependencies
4.0.3 - 2024-02-26
- Updated dependencies
4.0.2 - 2024-02-20
- When no Git commit hash is available, the SHA256 sum of the packaged tarball will now be used in its place. Previously, the string
unknown
was used and prevented pipeline promotions due to the same string being used for different versions. (#281)
4.0.1 - 2023-12-05
- 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)
- Workaround for JDK-8220723 that affected older (2019) OpenJDK versions. (#260)
4.0.0 - 2023-11-27
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.
- 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)
3.0.7 - 2023-02-06
- Update dependencies.
3.0.6 - 2022-12-01
- Update dependencies.
3.0.5 - 2022-10-26
- Update dependencies. (#142)
3.0.4 - 2020-08-11
- Fix
heroku:deploy-war
goal. (#77)
3.0.3 - 2020-07-09
- Add TLS workaround for OpenJDK 11.0.2. (#72)
3.0.2 - 2020-03-30
- Fix Microsoft Windows support. (#62)
3.0.1 - 2020-03-11
- Fix missing javadoc. (#59)
3.0.0 - 2020-03-11
- Extended documentation
- Extensive refactoring, but mostly compatible with 2.x. See below for breaking changes.
- HTTP_PROXY and HTTPS_PROXY environment variables are no longer respected. Use standard JVM proxy properties to configure HTTP proxies.
- System property
heroku.curl.enabled
removed. - Dropped support for Heroku Toolbelt on Windows. Use Heroku CLI instead.
- Support for
jvm-common
buildpack alias removed. Use standardheroku/jvm
instead.
2.0.16 - 2020-01-07
- Upgrade to Tomcat Webapp Runner 9.0.30.0
2.0.6 - 2018-08-27
- Upgrade to Tomcat Webapp Runner 8.5.33.0
- Update default buildpack URL
0.5.0 - 2015-07-14
- Upgraded to Tomcat 8 as default container
0.4.4 - 2015-07-01
- Added a warning for deploy-war when custom processTypes are present
0.4.3 - 2015-06-02
- Added ability to define custom buildpacks or multi-buildpack
- Accounted for Procfile's with empty lines in parsing
0.4.1 - 2015-05-12
- Added app name detection from Git repo.
0.4.0 - 2015-05-11
- Added ability to log incremental progress of slug upload.
0.3.6 - 2015-04-03
- Change config vars to overwrite existing values by default
- Ignore POM packaging if
warFile
config is set
0.3.5 - 2015-03-05
- Replaced javax.net with Apache HttpClient
- Improved default JAVA_TOOL_OPTIONS
0.3.4 - 2015-02-10
- Added
<includeTarget>
option to toggle the inclusion of thetarget/
directory by default
- Upgraded webapp-runner to 7.0.57.2
0.3.3 - 2015-02-09
- Added commit string to slug meta-data
0.3.2 - 2015-01-29
- Included with_jmap and with_jstack scripts.
- Added
heroku:create-slug
andheroku:deploy-slug
goals
0.3.1 - 2015-01-15
- Added
heroku:run-war
goal to run a WAR file locally with a command similar on Heroku - Added
heroku:dashboard
goal to open the Heroku dashboard for the configured application - Added
heroku:eclipse-launch-config
goal to generate Eclipse launch configuration files - Added caching of the JDK so it won't be downloaded on every deploy
- Began enforcement of
war
packaging when using-war
goals - Switched from custom MojoExecutor to org.twdata.maven:mojo-executor
0.3.0 - 2014-12-18
- Jumping to 0.3.x version to align with sbt-heroku
- Use explicit versions in pom.xml
- Remove support for Java 1.6
0.1.9 - 2014-12-02
- Improved detection of Heroku API key. Now uses .netrc first.