> For the complete documentation index, see [llms.txt](https://docs.meterian.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meterian.io/languages-support/java.md). # Java/Kotlin/Scala The Java+ analyser is triggered when one of the relevant manifest files is found in the root of the project. At this time it supports: * Maven : pom.xml * Gradle: build.gradle * Sbt: build.sbt * Ant: build.xml When using Maven. Gradle or Sbt, the tool will be actually invoked to generate the dependencies tree, as it's the only one who actually knows the components that, at the end of the day, will be really shipped. If you rely solely on the manifest files you will have to replicate what the tool is doing, which is really unreliable. The logic used is frequently just too convoluted, and only if you ask the tool to generate the dependencies tree you will be obtaining the right one. For that reason, your project has to build successfully before using Meterian. If this condition is not met then you won't be able to use this tool, so please make sure the project you want to attack is compiling correctly. When using Ant, the tool will first try to detect the dependencies using Ivy (if present): this allows the generation of a proper dependency tree. In any other case (or if the ivy approach fails) the tool will revert to a binary file detection strategy from the root of the project using the pattern "\*\*/\*.jar". In the report the dependencies will be listed by location. When using the [thin client](/the-client/client.md), the required tools will have to be installed and configured (Maven, Gradle, Sbt, Ant). This is not required when using the [dockerized client](/the-client/the-meterian-client-dockerized.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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.meterian.io/languages-support/java.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.