...
Problem
The SeaLights build scan needs the prefix of the packages in order to focus the scan only on your code and not include third-party code.
Sometimes you don't know what the package prefix is.
Solution
The Sealights build scanner provides the ability to can show you a list of prefixes in the java Java artifacts from the current working directory.
your application. You do so by using the following command:
| Code Block |
|---|
java -jar sl-build-scanner.jar -modules |
| Info |
This command requires to place the Sealights Build Scanner in the same working directory of the java artifacts analyzed. <path/to/jars/for/analysis> |
If you do not provide a path to the command it will analyze the files from the current working directory.
In the screenshot below, you'll see an illustration of the result from the modules command. for this specific artifact analyzed the relevant packages are highlighted.
The packages included parameter (-pi or -packagesincluded) used for the scan command of this artifact will be: "*com.kuhniverse.*"
...
Additional parameters
Additional options are available for this command:
| Code Block | |
|---|---|
| theme | Confluence | firstline | 1
| title | Command Reference | java -jar sl-build-scanner.jar -modules <path/to/jars/for/analysis> [-r] [-modulePathLength <arg>] |
Parameter | Description |
|---|---|
| Recursive |
search |
all |
folders |
under |
the |
workspace |
path | |
| Print modules with the length provided as a parameter (default value is 2). |
...
In the screenshot below, you'll see an illustration of the result from the modules command. for this specific artifact analyzed the relevant packages are highlighted.
The packages included parameter used for the scan of this artifact will be: "*com.kuhniverse.*"
Related articles
| Filter by label (Content by label) | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
|
...
|
...
| Page Properties | ||
|---|---|---|
| ||
|