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 level4, 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 level2, will print out information β¨-q,--quietβ quiet log level0, 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 level3, will print verbose logs (so many logs, so little time π)-w,--warnβ warn log level1, 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-shellto 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+onresolvemeans you can stack those<groupId> <artifactId> <version>triples, and the-ant/-dos/-shellflags 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 β¨π
π«Ά
π¦ where this page comes from
- debian bookworm: groovy 2.4.21-8 Β· Apache-2.0
- debian trixie: groovy 2.4.21-10 Β· Apache-2.0
- ubuntu jammy: groovy 2.4.21-1 Β· Apache-2.0
- ubuntu noble: groovy 2.4.21-10 Β· Apache-2.0
- ubuntu questing: groovy 2.4.21-10
- ubuntu resolute: groovy 2.4.21-10build1 Β· Apache-2.0
- ubuntu stonking: groovy 2.4.21-10build1 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms