MVN_BUILD(7)

💖 MVN_BUILD(7) — the mvn_build page, bestie edition 💖

okay so real quick: this is the manual page for mvn_build from the Java Packages Tools crew. she builds Maven projects with XMvn and she's lowkey the backbone of your whole spec file. let's get into it 🫶

---

✨ NAME ✨

mvn_build — build a Maven project with XMvn

---

🌸 SYNOPSIS 🌸

%mvn_build [options] [-- Maven-arguments]

---

🦋 DESCRIPTION 🦋

so the mvn_build macro does the thing: it builds your Maven project by calling XMvn, and then it generates the reactor structure information that mvn_install is gonna need later. they're a duo, fr fr. 💅

by default, Maven phase verify and goal javadoc:aggregate get executed, plus some extra XMvn-specific goals and phases on top. but if you pass -f? then phase package runs instead of verify. and if you pass -j? then goal javadoc:aggregate gets skipped entirely. choices, choices ✨

anything you put after -- gets passed directly to XMvn. if you wanna know what XMvn options are even available, go read xmvn(1). iykyk 👑

---

💅 OPTIONS 💅

• -d, --xmvn-debug — turn on XMvn debugging output. XMvn will write verbose debugging info to standard output. at minimum you'll get details about artifact resolution from system repositories. it's giving "let me see what's going on in here" 🔍
• -f, --force — skip compilation AND execution of unit and integration tests, and also skip resolution of build dependencies with scope test. this option makes Maven run phase package instead of the default phase verify, defines the property maven.test.skip=true (which disables compilation and execution of tests), and makes XMvn remove any project dependencies with scope test. no tests, no problem 😌
• -i, --skip-install — skip artifact installation. this disables generation of the reactor structure information, which means any future calls to mvn_install will not install the artifacts produced in the current Maven reactor. so like… nothing gets installed later. noted 💀
• -j, --skip-javadoc — skip javadoc generation. this skips running the Maven Javadoc Plugin. super useful for packages that don't wanna produce Java API documentation. no docs, no drama 🎀
• -s, --singleton — enable singleton packaging, aka one artifact per package. this makes artifacts with an identical artifactId get installed as part of the same subpackage. you can customize this behavior even further by adding more specific packaging rules with mvn_package. one artifact, one home, periodt 🏠
• -X, --debug — turn on Maven debugging output. this implies -d. Maven will write verbose debugging information to standard output. maximum yap mode, but make it useful 🔥

---

🌈 ENVIRONMENT 🌈

• xmvn_bootstrap — run XMvn in online mode. if the xmvn_bootstrap RPM macro is defined to any value, then XMvn runs in online mode. otherwise, XMvn runs in offline mode. online mode lets XMvn fetch missing dependency artifacts from remote repositories. this is mostly useful when you're bootstrapping new packages whose dependencies haven't been packaged yet. (yes, the original says "dependecies" — we're keeping the typo, that's canon now 🙈)
• _without_tests — defining this macro to any value is equivalent to the -f option.
• _without_javadoc — defining this macro to any value is equivalent to the -j option.

---

👑 AUTHOR 👑

originally written by Mikolaj Izdebski. versions 3.0.0 and later were written by Stanislav Ochotnicky. legends, both of them ✨

---

😭 REPORTING BUGS 😭

found a bug? don't suffer in silence, bestie. bugs should be reported through the Java Packages Tools issue tracker at Github:

https://github.com/fedora-java/javapackages/issues

---

🧚 SEE ALSO 🧚

mvn_alias(7), mvn_compat_version(7), mvn_config(7), mvn_file(7), mvn_package(7), xmvn(1).

---

and that's the whole page, bestie 🫶 this was JAVAPACKAGES, dated 2025-09-19, and yes the manual name really is MVN_BUILD(7) — go build something iconic with it 💖✨🌸