The SeaLights Maven plugin is designed to wrap the entire process (Build Scan + Test Listener functions) into the Maven lifecycle, allowing seamless integration with the build tool.
This solution uses the build scanner .jar file as well as a JSON configuration file. Once the jar is executed specifying the configuration file, the pom.xml files of the Maven project are altered to incorporate the SeaLights plugin. This can be reversed using another CLI command. Please refer to the dedicated page Recommended - Automatic configuration of Maven via a JSON file to proceed with the integration.
Selaights Maven plugin operates in the following Maven lifecycle stages:
Build Scanner is executed during
process-classes
Tests executed during the
test
phase are capturedSealights files (token and builldSessionId) are added to the artefact during the
package
phase
Test Runner versions
The following versions are the minimum required for integration with Maven test runners:
Surefire - version 2.8 and above
Here is the entire list of articles in this sub-section:
Legacy integration method
There is another method kept for backward compatibility (Legacy - Defining a Sealights profile in the pom.xml file) that includes an example that needs to be defined manually within the selected pom.xml files.
If you're onboarding a new application please avoid this method.