Notice

This guide is for the original release of AQtive Guard. For the current AQG SaaS platform, go to the AQtive Guard User Guide.

Maven Plugin changelog

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.

0.12.1 - 2024-06-07

Fixed

• Fix published POM file to include a proper <version> tag and no development-specific information. This makes it more easily consumable by repositories such as Nexus.

0.12.0 - 2024-02-29

Changed

• Use a temporary GZIP file to store the concatenated trace files instead of storing them in RAM.
• Drop the dependency on the Apache commons-io library.
• Update the Java Tracer to 2.1.0.

0.11.0 - 2023-12-19

Changed

• Update Java API client to 2.1.1 to fix compatibility with AQtive Guard (versions 23.09.7 and later versions). This breaks compatibility with versions before 23.09.7.
• Update Java tracer to 2.0.5.

0.10.0 - 2023-07-12

Changed

• Update Java API client to 2.1.0 to only retrieve report metadata and statistics instead of actual instances (the latter could potentially cause the final request from the plugin to time out).

0.9.3 - 2023-03-22

Changed

• Update Java Tracer to 2.0.3

0.9.2 - 2022-10-10

Changed

• Update Java API client to 2.0.0 (it comes with updated dependency version constraints for easier use in corporate artifact repositories).

Fixed

• Fix output for Maven versions before 3.5.0 (when terminal color codes are not interpreted correctly).
• Fix error message when a report isn’t found (thanks to the update of the API client to version 2.0.0).

0.9.1 - 2022-09-26

Fixed

• Fix error when tracing applications with the plugin.

0.9.0 - 2022-08-03

Changed

• Update Java Tracer to 2.0.2.
• Update Java API Client to 1.0.3.

0.8.0 - 2021-03-08

Changed

• Update Java Tracer to 1.8.1.
• Update Java API Client to 1.0.2.

0.7.0 - 2021-01-14

Changed

• Update Java Tracer to 1.6.3.

0.6.0 - 2020-01-14

Changed

• Update api-client to 1.0.0: This uses the new GraphQL v2 API of the SandboxAQ Security Suite.

Removed

• Remove the reportPath option. The report.json file is not created anymore.

0.5.2 - 2019-11-14

Changed

• Update java-api-client to 0.2.4

0.5.1 - 2019-08-12

Changed

• projectId parameter no longer constrained to an integer, to accomodate for new dynamic trace streaming

0.5.0 - 2019-07-18

Added

• New uploadDomain property: if present, stream the application trace directly to the specified domain, rather than storing it in a file. Note: When streaming trace data, it is not possible to generate a report as part of a build.
• New uploadPort property: override the default remote port (port 80) when streaming the application trace.
• New uploadUseTls property: use a TLS socket when streaming the application trace (default: false).

Changed

• Update java agent to 1.5.1.

Removed

• The uploadEndpoint property has been replaced with the new uploadDomain, uploadPort and uploadUseTls properties

0.4.1 - 2019-07-10

Changed

• By default, report.json is now saved to ${project.basedir}

0.4.0 - 2019-07-09

Added

• Add a new aggregate-report mojo to enable the generation of reports in a multi-module scenario

0.3.1 - 2019-06-26

Added

• Add the ability to stream trace data to a remote server. To support this, a new uploadEndpoint property has been added. When this property is set, the agent will be configured to stream trace data directly to uploadEndpoint, rather than storing storing it on disk. Note: When streaming trace data, it is not possible to generate a report as part of the build.

0.3.0 - 2019-06-14

Added

• By default, the agent injection goal will now delete the trace output directory before the tests are run, in order to prevent duplicate trace upload. This can be disabled using a new deleteTraceDirectoryBeforeTests boolean configuration option
• Add the option to enforce the presence of traces using the ensureTracesPresent property (default: false)

Changed

• The default value of agentOutputPrefix has changed from cs-trace to ${project.artifactId} to make report differentiation easier in multi-module projects
• Fix an issue where an empty trace directory would cause a plugin crash
• All mojos are now marked as thread-safe

0.2.3 - 2019-06-11

Changed

• Restore relaxed Maven version prerequesites to 3.3.9

0.2.2 - 2019-06-04

Changed

• Use Java API Client 0.2.3.

0.2.1 - 2019-05-28

Added

• Output the analysis results to disk as well as printing them to terminal. The output location can be set using the reportPath property (default: ${project.build.directory}/report.json)

Changed

• Use Java Tracer 1.4.0.
• Update dependencies.

Fixed

• If the target/cs-tracer directory is missing, then the plugin will warn about this and allow the build to continue (rather than raising an exception).

0.2.0 - 2019-01-14

Added

• Add the option to configure the minimum instance severity used to determine pass or failure of the build using the failBuildOnInstanceSeverity property (default: low)

0.1.0 - 2018-12-17

Added

• Add the option to configure the trace output directory using the optional agentOutputDirectory property (default: ${project.build.directory}cs-tracer)
• Add the option to configure the trace output prefix using the optional agentOutputPrefix property

Changed

• Update dependencies

0.0.4 - 2018-11-19

• Update dependencies

0.0.3 - 2018-11-05

• Fix broken agent path computation

0.0.2 - 2018-10-31

Changed

• Update dependencies

0.0.1 - 2018-10-19

Added

• Initial version of the plugin