MAVEN(1)

πŸ“¦
version 1.12 Β· 3 versions
, in ubuntu resolute, ubuntu stonking

πŸ‘‘ MAVEN β€” the manual page, but make it make sense πŸ’…

okay so bestie, you opened MAVEN(1) from User Commands and honestly? you're about to have a great time. this is the glow-up version, but every single fact is still here, no cap. 🫢


✨ NAME ✨

Maven β€” installs all POMs for the package into /usr/share/maven-repo. that's it, that's the whole job. iconic behaviour fr fr.


🌸 SYNOPSIS 🌸

mh_installpoms [option]...

literally just run it with some options, she'll handle the rest πŸ’–


πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the vibe: it reads the file debian/$package.poms, and then installs every single POM file listed in that .poms file. that's the whole plot. no plot twists. 🌈


πŸŽ€ OPTIONS πŸŽ€

  • -h, --help β€” show this text ✨
  • -V, --version β€” show the version πŸ‘‘
  • -p<package>, --package=<package> β€” name of the Debian package which will contain those POM files πŸ“¦
  • -k, --keep-pom-version β€” keep the original version of the POM but convert all other versions in dependencies and plugins. if there is a parent POM, it keeps its version β€” except when the parent is already registered in the Maven repository πŸ‘€
  • -e<version>, --set-version=<version> β€” set the version for the POM, and do not use the version declared in the POM file. you're the main character now, you decide πŸ’…
  • -r<rules>, --rules=<rules> β€” path to the file containing the rules to apply when cleaning the POM. optional, the default location is debian/maven.rules 🧹
  • -u<rules>, --published-rules=<rules> β€” path to the file containing the extra rules to publish in the property debian.mavenRules in the cleaned POM. optional, the default location is debian/maven.publishedRules πŸ“’
  • -i<rules>, --ignore-rules=<rules> β€” path to the file containing the rules used to remove certain dependencies from the cleaned POM. optional, the default location is debian/maven.ignoreRules πŸ™ˆ
  • -c<rules>, --clean-ignore-rules=<rules> β€” path to the file containing the rules use to remove certain dependencies from the cleaned POM, in addition to the ignore rules specified previously. this is useful in situations such as when the Maven clean target requires more dependencies or plugins to ignore than the build target. all rules defined in clean-ignore-rules will be added to the existing rules in ignore-rules. optional, the default location is debian/maven.cleanIgnoreRules 🧼
  • -s, --no-rules β€” don't apply any rules for converting versions, and do not even convert versions to the default debian version 🚫
  • --no-publish-used-rule β€” don't publish the rule used to transform a POM's own attributes in debian.mavenRules 🀫
  • --keep-elements=<elem1,elem2> β€” keep the elements listed here even if they are normally removed by the clean operation. such elements are build,reports,reporting,prerequisites,profiles. βœ‹
  • -m<repo root>--maven-repo=<repo root> β€” location of the Maven repository, used to force the versions of the Maven plugins used in the current POM file with the versions found in the repository πŸ—‚οΈ
  • -v, --verbose β€” show more information while running πŸ—£οΈ
  • -n, --no-act β€” don't actually do anything, just print the results πŸ‘» (a little peek, no commitment)

πŸ’œ SEE ALSO πŸ’œ

See also: mh_installpom(1), mh_cleanpom(1) β€” go say hi to the siblings, they're family 🫢


lowkey obsessed with you for reading the whole thing. now go install those POMs, bestie πŸ’–

Maven Repo Helper version 1.7.1 β€” September 2025 🌸 that's the whole sign-off, mwah, slay, periodt πŸ’…βœ¨

πŸ“¦ where this page comes from