> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/java/which-packages-to-configure.md).

# Which Packages to Configure?

I don't know what packages to configure

## Problem <a href="#problem" id="problem"></a>

The SeaLights build scan needs the prefix of the packages 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 <a href="#solution" id="solution"></a>

The Sealights build scanner can show you a list of prefixes in the Java artifacts from your application. You do so by using the following command:

{% code overflow="wrap" lineNumbers="true" %}

```sh
java -jar sl-build-scanner.jar -modules <path/to/jars/for/analysis>
```

{% endcode %}

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.*"`

<figure><img src="https://4057366433-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAjqTCMRYvHhDgsdPLUnc%2Fuploads%2F8mhXIaLpS83aWkfzAmsU%2Fimage2019-9-22_12-57-54.png?alt=media&amp;token=5a85cd4d-9c87-49e8-ab2f-61b24373e54c" alt=""><figcaption></figcaption></figure>

### Additional parameters <a href="#additional-parameters" id="additional-parameters"></a>

Additional options are available for this command:

{% code overflow="wrap" lineNumbers="true" %}

```sh
java -jar sl-build-scanner.jar -modules <path/to/jars/for/analysis> [-r] [-modulePathLength <arg>]
```

{% endcode %}

| `r`                | Recursive search all folders under the workspace path                                                                                                                                        |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `modulePathLength` | <p>Print modules with the length provided as a parameter (default value is 2).<br>For example, two significant names will appear as <em>io.sealights. and single will appear as io.</em></p> |

## Related articles <a href="#related-articles" id="related-articles"></a>

* [Pivotal Cloud Foundry (PCF) Support](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/java-agent/pivotal-cloud-foundry-pcf-support.md)
* [NodeJS - JavaScript heap out of memory](/knowledgebase/setup-and-configuration/troubleshooting-faq/node-javascript/nodejs-javascript-heap-out-of-memory.md)
* [Testing Frameworks Integration](/knowledgebase/setup-and-configuration/integrations/testing-frameworks-integration.md)
* [Installing the Coverage Listener as a JVM Java Agent](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/java-agent/default-usage-cli/installing-the-coverage-listener-as-a-jvm-java-agent.md)
* [Legacy CD Agent for Java Application](/knowledgebase/setup-and-configuration/sealights-agents-and-plugins/cd-agent/cd-agent-for-java-application.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/java/which-packages-to-configure.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.