we need JAR dependency manager like Grape for ApacheGroovy i.e., ‘@Grab’
Do we really?
Searching for “Grab” in groovy files roughly has 8000 results, the actual number of files are less and projects even fewer.
Searching for build.gradle gives us far over a million results.
And a search for pom.xml gives us nearly 2 million results
These results are far from statistical accurate, but gives us a rough idea how this approaches are used. Seems that grapes are just too sour for most peoples taste.
Well it would be nice declarering all dependencies along with code in a single file when writing self executable kotlin scripts .kts
It looks like this lib https://github.com/holgerbrandl/kscript . . has got you covered
If using kotlin in a scripting mode is a serious use-case, then so is this suggestion.
Grapes and Grab (groovy scripting in general, as opposed to projects that use groovy more like java is used) are mostly used for personal or internal scripting automations, much like an experienced systadmin’s personal arsenal of bash scripts. Such things are not frequently shared, so I’m not sure looking at projects the way you are is a useful measure of this idea’s legitimacy.