-
Detect SDK dependency version mismatches (#126)
- The new
validateSdkDependencyVersions
goal verifies that all of the Sentry SDK dependencies included in yourpom.xml
have consistent versions - We recommend enabling this goal by adding
within your
<executions> <execution> <goals> <goal>validateSdkDependencyVersions</goal> </goals> </execution> </executions>
plugin
tag forio.sentry:sentry-maven-plugin
- The build will fail in the
validate
lifecycle phase if a version mismatch is detected - You can opt out of this check by disabling the
validateSdkDependencyVersions
goal or by addingwithin your<configuration> <skipValidateSdkDependencyVersions>true</skipValidateSdkDependencyVersions> </configuration>
plugin
tag forio.sentry:sentry-maven-plugin
. This is not recommended, as using mismatched versions of the Sentry dependencies can introduce build time or run time failures and crashes.
- The new
-
Upgrade internal Sentry SDK to 8.4.0 (#134)
- Bump CLI from v2.41.1 to v2.43.0 (#125, #129, #132, #141, #144)
- Bump Sentry SDK from v8.2.0 to v8.5.0 (#130, #135, #140)
- Add AutoInstallStrategy for graphql-22 (#100)
- More lenient handling of empty Maven modules (#103)
- The Maven plugin now ignores Maven modules with empty source roots and instead of failing the build simply prints a log message
- This allows the plugin to be configured in the root POM even if it does not have sources
- Bump Sentry SDK from v7.8.0 to v8.0.0 (#78, #86, #97, #99, #104, #111, #113, #115, #120)
- Bump CLI from v2.31.2 to v2.41.1 (#76, #85, #87, #90, #91, #96, #98, #101, #102, #109, #114, #119)
- Disable source upload via
SENTRY_SKIP_SOURCE_UPLOAD
environment variable (#65)
- Bump Sentry SDK from v7.3.0 to v7.8.0 (#55, #56, #59, #72)
- Bump CLI from v2.28.6 to v2.31.2 (#58, #63, #67, #68, #69, #74)
- Change telemetry DSN to point to production project (#54)
- Bump Sentry SDK from v7.0.0 to v7.3.0 (#40, #45, #49)
- Bump CLI from v2.23.0 to v2.28.6 (#41, #42, #43, #44, #46, #47, #48, #50, #51, #52, #53)
- Report dependencies (#22)
- Send telemetry data for plugin usage (#28)
- This will collect errors and timings of the plugin and its tasks (anonymized, except the sentry org id), so we can better understand how the plugin is performing. If you wish to opt-out of this behavior, set
<skipTelemetry>true</skipTelemetry>
in the sentry plugin configuration block.
- This will collect errors and timings of the plugin and its tasks (anonymized, except the sentry org id), so we can better understand how the plugin is performing. If you wish to opt-out of this behavior, set
- Add
aarch64
sentry-cli (#39)- This is used when the build is executed inside a docker container on an Apple silicon chip (e.g. M1)
- Allow usage of the plugin with JDK 8 (#37)
- Add
debug
flag (#38)
- Bump Sentry SDK from v6.32.0 to v7.0.0 (#23, #24, #29, #32)
- Bump CLI from v2.21.2 to v2.23.0 (#25, #27, #30, #31, #35)
- Add parameter to skip plugin execution (#17)
- Auto-Install Sentry and Sentry integrations using Maven build extension (#10)
- Auto-Update
sentry-cli
and Sentry Java SDK version (#12)
- Download and Bundle sentry-cli with maven plugin (#8)
- Add support for building on Windows (#7)
- Also use
url
andauthToken
for upload command (#7)
- Initial version of sentry-maven-plugin