MAVEN(1)

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

πŸ’– MAVEN(1) β€” like, the maven manual page, bestie πŸ’–

okay so this is a User Commands situation, and the whole vibe is: Maven, but make it Debian packaging. πŸŽ€ let's go.


✨ NAME ✨

Maven β€” patches one POM file using the Maven dependency rules. that's it, that's the whole job. 🫢


🌸 SYNOPSIS 🌸

mh_patchpom [option]... [pom] [backup]

πŸ¦‹ DESCRIPTION πŸ¦‹

bestie. what this does is transform the POM using the transformation rules. slay. periodt. πŸ’…

and here's where everything lives:

  • [pom] is the location of the POM file to transform.

Defaults to pom.xml

  • [backup] is the backup file for the pom.

Defaults to pom.xml.save

like, if you don't tell it otherwise, it's gonna assume pom.xml and pom.xml.save. no cap. ✨


πŸ‘‘ OPTIONS πŸ‘‘

  • -h, --help β€” show this text. iconic behaviour, honestly.
  • -V, --version β€” show the version. so you know what you're working with. 🌈
  • -p<package>, --package=<package> β€” name of the Debian package which will contain this POM file.
  • -o, --no-parent β€” don't inherit from a parent POM. cutting the apron strings fr fr. 🧚
  • -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, 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, do not use the version declared in the POM file. we're overriding, bestie. πŸ’œ
  • -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.
  • -R<rule>, --extra-rule=<rule> β€” extra rule to apply when cleaning the POM.

May occur multiple times, instead of or in addition to -r. stack 'em. πŸ”₯

  • -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.
  • -U<rule>, --extra-published-rule=<rule> β€” extra rule to publish.

May occur multiple times, instead of or in addition to -u. yes, again, multiple times. we love a repeatable flag. πŸŽ€

  • -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.
  • -I<rule>, --extra-ignore-rule=<rule> β€” extra rule used to remove dependencies from the transformed POM. May occur multiple times, instead of or in addition to -i.
  • -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, do not even convert versions to the default 'debian' version. going feral, no rules, chaos mode. πŸ’€
  • --no-publish-used-rule β€” don't publish the rule used to transform a POM's own attributes in debian.mavenRules.
  • -d, --debian-build β€” transform during a Debian build, which means that some POM elements will be removed.
  • -b, --build-no-docs β€” if the build doesn't need to build documentation, use this option to remove some POM elements (in particular plugins) which are useless here and may require extra dependencies and make the packaging harder.
  • -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. main character energy: tell me EVERYTHING. πŸ™ˆ
  • -n, --no-act β€” don't actually do anything, just print the results.
lowkey the safest flag in the whole page. nothing happens, you just get to look. do a vibe check before you commit, bestie. 🫢

πŸ’« SEE ALSO πŸ’«

See also: mh_installpom(1), mh_patchpoms(1)


and that's the whole page!! πŸ“ it's giving Maven Repo Helper version 1.7.1, dated September 2025, and honestly? iconic. go patch a POM. you got this. πŸ’–βœ¨πŸ‘‘

πŸ“¦ where this page comes from