...
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 page Recommended - Automatic configuration of Maven via a JSON file to proceed with the integration.
Selaights Sealights Maven plugin operates in the following during specific Maven lifecycle stages phases:
Build Scanner is executed during
process-classesTests executed during the
testphase are capturedSealights' files (token
sltokenandbuilldSessionId) are added to the build artefact during thepackagephase (IncludeResourcesoption).
...
| Note |
|---|
The following versions are the minimum required for integration with Maven test runners:
|
Here is the entire list of articles in this sub-section:
| Child pages (Children Display) | ||
|---|---|---|
|
...
Legacy integration method
...
In addition to the ‘automatic update of POM file', we have kept backward compatibility of integrating Sealights plugin with your Maven build manually as described in Legacy - Defining a Sealights profile in the pom.xml file
...
.
This solution requires to manually edit your project’s pom.xml files
...
and add explicitly the Sealights plugin definition and settings. If you're onboarding a new application please avoid this method.
Here is the entire list of articles in this sub-section:
| Child pages (Children Display) | ||
|---|---|---|
|