Dependency format and Maven central

[aghasemi]

Hi,
In the docs, it is said that dependencies follow the "gradle-style locator" format. However, neither of the formats provided in Maven central can be used in JBang without change. Am I right? For example, for Gradle Short I have to manually remove implementation and the single equations.

This is another lazy-person's question maybe, but I just thought I may have missed something.

[quintesse]

Indeed. I think what the docs mean by Gradle-style is the group:artifact:version format with the colons separating the values.

I think you can use the "Groovy Grape" ones exactly as mentioned though (but I've personally never used that format so I'm not sure).

[aghasemi]

Yes. But that requires an extra import statement, plus a @GrabResolver annotation, and I think one shall have only one @Grapes annotation (no?), so copy/paste from Maven central again breaks from second dependency onward.

The closest format to DEPS seems to be that of Buildr (e.g. 'junit:junit:jar:4.13.2'), which has added only single quotes and a :jar identifier. Maybe JBang can accept this string as is, without one having to remove single quotes and :jar substring manually?

[maxandersen]

If your issue is that search.maven.org does not show something directly copy/pastable then:

1. Wait for add jbang dependency option sonatype-nexus-community/search-maven-org#137 to be merged (was approved back in 2021) then jbang format will show up
2. run jbang app install gavsearch@jbangdev and use gavsearch hibernate-orm to find GAV's and return i it in gradle,maven,jbang style formats.

about supporting 🫙 format then I don't think bad UI on search.maven.org justifies the complexity it would bring.

[aghasemi]

1. Wait for add jbang dependency option sonatype-nexus-community/search-maven-org#137 to be merged (was approved back in 2021) then jbang format will show up

That's indeed the perfect solution!