Is the java client development far behind the golang one?

[LeiYangGH]

The golang one(https://github.com/jfrog/jfrog-cli) is really nice to use, I like the batch upload/download function very much, it can easily

1. specify sub folder name and artifact name by wildcards --- while the java version can only search artifact name)
2. batch download above artifacts specifying number of threads, flat or nested folder structure, etc --- java version can do none.
3. there should be more...
4. the metioned lacking functions in java version may exist somewhere(for incidence i saw aql functions from the source code), but at least they aren't in the document or the samples.

So I'm curious why golang version goes much ahead than java version. aren't they both developed by jfrog developers?

[stegeto22]

I'm interested in getting an answer, too.

[eyalbe4]

@LeiYangGH and @stegeto22, The main reason why the jfrog-client-go library is ahead of artifactory-client-java library, in terms of features and capabilities, is because JFrog CLI heavily relies on it. It therefore gets more attention by developers, both internal and external to JFrog. We would love to see the java client receive more attention through community contributions. I agree, it would be great if many of the features developed for the go client are also added to the java one.