grape(1)

πŸ‡ grape(1) β€” the local grape cache glow-up πŸ’…

okay bestie, so like... this is the manual page for grape, a General Commands Manual situation, and it's genuinely the moment you learn how the local grape cache used by Groovy works. no cap. 🫢


✨ NAME ✨

grape β€” inspection and management of the local grape cache used by Groovy 🌸


πŸ¦‹ DESCRIPTION πŸ¦‹

here's the whole vibe, the literal usage:

usage: grape [options] <command> [args] options:

and then the options themselves, which are iconic, lowkey essential:

  • -D, --define <name=value> β€” defines a system property, periodt πŸ’…
  • -d, --debug β€” debug log level 4, and it will print out full stack traces (yes, all of them, buckle up 😭)
  • -h, --help β€” gives you the usage information, i.e. the little map of your life πŸŽ€
  • -i, --info β€” info log level 2, will print out information ✨
  • -q, --quiet β€” quiet log level 0, will print only errors (silence... but make it error-only 🀫)
  • -v, --version β€” displays the Groovy and JVM versions, v v useful 🌈
  • -V, --verbose β€” verbose log level 3, will print verbose logs (so many logs, so little time πŸ’€)
  • -w, --warn β€” warn log level 1, will print only errors and warnings ⭐
not me listing every single log level... but fr fr, -q = 0, -w = 1, -i = 2, -V = 3, -d = 4. the escalation is real and it's giving character development πŸ‘‘

πŸ‘‘ COMMANDS πŸ‘‘

  • install <groupId> <artifactId> [<version>] β€” this installs the specified groovy module or maven artifact. if a version is specified, that specific version will be installed; otherwise the most recent version will be used (as if '*' we passed in). πŸ“
  • list β€” lists locally installed modules (with their full maven name in the case of groovy modules) and versions. main character energy, honestly πŸ¦‹
  • resolve (<groupId> <artifactId> <version>)+ β€” this returns the file locations of the jars representing the artifcats for the specified module(s) and the respective transitive dependencies. you may optionally pass in -ant, -dos, or -shell to get the dependencies expressed in a format applicable for an ant script, windows batch file, or unix shell script respectively. πŸ’…
okay so like, note that the + on resolve means you can stack those <groupId> <artifactId> <version> triples, and the -ant / -dos / -shell flags are the ones you optionally pass in for the different output formats. iykyk 🧚

🌸 SEE ALSO 🌸

  • groovy(1) β€” go be obsessed with that one too πŸ’–

πŸ’œ AUTHOR πŸ’œ

this manual page was generated using help2man and edited by Ludovic Claude <ludovic.claude@laposte.net>, for the Debian project (but may be used by others). πŸŽ€


and that's the whole page, bestie β€” this was the grape(1) manual page from July 2009, living under the General Commands Manual umbrella, and we ate. no crumbs. slay βœ¨πŸ’…πŸ«Ά