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.
6.0.3 - 2024-09-26
- No changes.
6.0.2 - 2024-09-25
- No changes.
6.0.1 - 2024-07-19
- No changes.
6.0.0 - 2024-05-28
- Some error messages have changed so they longer suggest to open a Heroku support ticket. Instead, users are now provided with a link to create an issue on GitHub. (#674)
5.0.1 - 2024-05-23
- No changes.
5.0.0 - 2024-05-23
- Support for the
arm64
architecture. (#668)
- Buildpack API version changed from
0.9
to0.10
, and so requireslifecycle
0.17.x
or newer. (#662)
4.1.1 - 2024-05-01
- No changes.
4.1.0 - 2024-01-23
- No changes.
4.0.2 - 2023-12-05
- No changes.
4.0.1 - 2023-12-04
- No changes.
4.0.0 - 2023-10-25
- No changes.
3.2.2 - 2023-10-24
- Updated buildpack display name, description and keywords. (#603)
3.2.1 - 2023-10-19
- No changes.
3.2.0 - 2023-09-20
- No changes.
3.1.0 - 2023-09-18
- No changes.
3.0.0 - 2023-08-09
- Remove support for installing Maven
3.2.5
,3.3.9
,3.5.4
and3.6.2
viasystem.properties
. These versions of Maven contain security vulnerabilities and should not be used. Users that cannot upgrade to a secure version of Maven can install the Maven Wrapper for the required Maven version to their application (i.e.mvn wrapper:wrapper -Dmaven=3.6.2
). (#556)
- Default version for Maven is now
3.9.4
. (#556)
2.0.0 - 2023-07-31
- No changes.
1.1.2 - 2023-07-24
- No changes.
1.1.1 - 2023-06-22
- No changes
- This buildpack now declares to be compatible with the
*
stack. While the buildpack cannot guarantee it works with any stack conceivable, it should be compatible with some stacks that are not maintained by Heroku. Use of this buildpack on such stacks is unsupported. (#498) - Allow
JAVA_HOME
to be set by user or operator via<platform>/env
. (#508) MAVEN_SETTINGS_PATH
,MAVEN_ESTTINGS_URL
,MAVEN_CUSTOM_GOALS
, andMAVEN_CUSTOM_OPTS
can be set by a previous buildpack. (#508)
- Upgrade
libcnb
andlibherokubuildpack
to0.12.0
. (#463) - The buildpack now implements Buildpack API 0.9 instead of 0.8, and so requires
lifecycle
0.15.x or newer. (#463)
- Upgrade
libcnb
andlibherokubuildpack
to0.11.0
. (#371) - Buildpack now implements buildpack API version
0.8
and so requires lifecycle version0.14.x
or newer. (#363)
- Updated
libcnb
andlibherokubuildpack
to0.9.0
. (#330) - Switch to the recommended regional S3 domain instead of the global one. (#314)
- Upgrade
libcnb
to0.8.0
andlibherokubuildpack
to0.8.0
.
- Add support for the
heroku-22
stack. (#304)
- Re-implement buildpack using libcnb.rs (#273)
- Source and Javadoc JAR files are no longer considered when determining the default web process. (#273)
- Switch to BSD 3-Clause License
- Applications that use Spring Boot are now properly detected even if their dependency to Spring Boot is transitive
- Ensures
mvnw
is executable
- Loosen stack requirements allowing any linux distro use this buildpack
- Documentation in
README.md
M2_HOME
environment variable is now set for subsequent buildpacks if Maven was installed.MAVEN_OPTS
environment variable will be set for subsequent buildpacks to allow the use of the local repository layer without explicit configuration.
- Fixed
licenses
inbuildpack.toml
- No changes.
- Automated post-release PRs
- Now requires (in the CNB sense)
jdk
to pass detection - Now provides (in the CNB sense)
jvm-application
to subsequent buildpacks
- Debug logging, can be enabled by setting
HEROKU_BUILDPACK_DEBUG
environment variable
- Code refactoring
- Logging style now adheres to Heroku's CNB logging style
- Maven options that are implementation details are no longer logged by default
- Maven options that are required for proper operation of this buildpack can no longer be overridden by
MAVEN_CUSTOM_OPTS
orMAVEN_CUSTOM_GOALS
- Caching of Maven dependencies
- Exit code of
bin/detect
when detection failed without an error
- Initial release