MAVEN(1)

πŸ’– MAVEN(1) πŸ’–

okay bestie, sit down, hydrate, and let me tell you about MAVEN β€” it's a User Commands manual page, and yes it lives in section 1 of the manual, and yes it's giving very niche-but-important. This is the man page for Maven Repo Helper version 1.7.1, and honestly? She's a little legend. 🫢


✨ NAME ✨

Maven β€” manual page for Maven Repo Helper version 1.7.1 πŸ’…


🌸 SYNOPSIS 🌸

mh_lspoms [option]... <package>

like. that's the whole vibe. one command, some options, a package. iconic.


πŸ¦‹ DESCRIPTION πŸ¦‹

So what does she actually do? She looks for all POM files defined in the source of the project. All of them. Every last one. She's thorough like that. πŸ‘‘

Where:

  • <package> is the name of the binary package,

e.g. libcommons-lang-java. Default to the first binary found in the debian/control file.

ngl the default is lowkey doing the most for you β€” if you don't tell her which package, she just grabs the first binary she finds in debian/control. convenient!! πŸŽ€

πŸ’… OPTIONS πŸ’…

  • -h, --help β€” show this text. the classic. the "help me help you" button. πŸ’–
  • -V, --version β€” show the version. so you can be like "which one am I even running" and she'll tell you. ✨
  • -p<package>, --package=<package> β€” package to act on. you pick who we're talking about. 🌸
  • -f, --force β€” force run even if the .poms files exist.

Only maven.rules will be created, assuming that it did not exist before.

bestie READ this one. force mode doesn't redo everything, okay? it only makes maven.rules, and only if it wasn't there before. don't come for me if you expected more. 😭
  • -n, --non-interactive β€” non interactive session, don't ask questions. she just goes. no small talk. main character energy, zero interruptions. πŸ’€
  • -o, --offline β€” don't ever connect to the internet, for Debian build compatibility. offline queen. no wifi, no problem, purely for Debian build compatibility. 🌈

You need to execute it on the unpacked origial source tree, merged with the debian/ folder. (yes, "origial", I said what the page said, don't @ me πŸ™ˆ) It will create the file debian/<binary package>.poms which contains all the POMs to deploy to the Maven repository and is used by mh_installpoms.

The contents of debian/<binary package>.poms should be:

  • one POM file location per line,
  • optionally, the location is followed by the option --no-parent

to indicate that if this POM inherits from a parent, the parent element will be removed.

so like, one path per line, and if you tack --no-parent on the end of a line, that POM's parent element gets yeeted if it inherits from one. slay. 🧚

Maven Repo Helper version 1.7.1 🌟 September 2025 🌟 and that's the whole page, bestie β€” go forth, list those POMs, and remember: the manual name is MAVEN, section 1, and she ate. πŸ’œ

πŸ“¦ where this page comes from