javawrapper(1)

💖 javawrapper — bestie edition 💖

okay so you found your way to javawrapper(1), the General Commands Manual page, and honestly? slay. this is the manual for the Jar daemon wrapper, and i'm about to walk you through it like we're texting at 2am. no cap, every single flag stays. let's go 🦋

✨ NAME ✨

wrapper — Jar daemon wrapper 💅

like, it wraps your jar. it daemonizes. it's giving main character energy for your Java app.

🌸 USAGE 🌸

wrapper [<command>] [<configuration file>] [<configuration properties>]

and <command> can be one of these, bestie:

• -c, --console — run it as a Console application 🖥️ (no daemon-ing, just vibes in your terminal)
• -v, --version — prints the wrapper's version info. the receipts, basically 📜
• -?, --help — prints this help message, i.e. the manual you're already reading, iconic 🔁
• -- <args> — marks the end of the Wrapper arguments. everything after the -- gets passed through unmodified straight to the java application. untouched. pristine. periodt ✨

<configuration file> is the wrapper.conf you wanna use. the filename has to be either absolute or relative to the location of wrapper. no guessing games 🎀

<configuration properties> are configuration name-value pairs that override values in wrapper.conf. for example:

wrapper.debug=true

look at her go 💅

⚠️ please note, bestie: any file references must be either absolute or relative to the location of the wrapper executable. that's the rule. i don't make them, i just report them fr fr 💀

🫶 AUTHORS 🫶

this manual page was written by Rémi Debay <debay.remi@gmail.com> and Kill Your TV <killyourtv@i2pmail.org>. legends only 👑

that's the whole page, you ate it up 🌈 this lil manual came from javawrapper(1), dated 12/24/2012, so go forth and wrap those jars, bestie — bye bestie, drink water, and remember: absolute paths or relative-to-wrapper-executable paths, nothing in between 💖✨