mvn-generate-sources

mvn generate-sources [options]

mvn generate-sources invokes Maven's generate-sources lifecycle phase, which (along with all earlier phases — validate, initialize) runs any plugin executions bound to it. This is where code generators belong: JAXB / XJC, gRPC / Protocol Buffers, Avro, Antlr, OpenAPI, Modello, JOOQ, etc. Generated sources usually land under target/generated-sources/plugin/ and are added to the compile source roots automatically when the next phase, process-sources → compile, runs.Because Maven runs every preceding phase as well, mvn generate-sources is rarely the most useful command on its own — most users invoke mvn compile or mvn package and let generation happen as a side effect. Use this phase explicitly when you want generated code available for IDE refresh without compiling the whole project.

-P profile[,profile...]

Activate one or more build profiles defined in pom.xml or settings.xml.

Work offline (do not contact remote repositories).

Force a check for updated SNAPSHOT dependencies and plugin releases.

Enable debug-level Maven output.

Restrict the build to the listed reactor modules (comma-separated).

Build also the projects required by the ones selected with -pl.

Use N threads, optionally per CPU core (e.g. -T 1C).

Pass a system property to the build.

Generated sources are wiped by mvn clean. Plugins must be bound to generate-sources in pom.xml or activated by a profile; otherwise nothing happens. Multiple plugins generating into the same root can collide.

mvn(1), mvn-compile(1), mvn-package(1), mvn-dependency(1)