Java: Update README for local maven installation instructions

[acarbonetto]

No description provided.

[jamesward]

Since the artifacts aren't available in Maven Central yet, this is a possible temporary workaround, but I don't think this should go into a README as this is not a typical or recommended way to consume the artifacts.

[acarbonetto]

Since the artifacts aren't available in Maven Central yet, this is a possible temporary workaround, but I don't think this should go into a README as this is not a typical or recommended way to consume the artifacts.

Yes. Agreed. We will want to remove this (or move to the Developer.md for how to use the ExampleApp) as soon as the Maven Central artefacts are up and available.

[jamesward]

I'm having an issue getting classifier resolution to work with this approach. Trying to see if I can make it work with install:install-file and will report back.

[acarbonetto]

I'm having an issue getting classifier resolution to work with this approach. Trying to see if I can make it work with install:install-file and will report back.

You can use (for classifier osx-aarch_64):

mvn install:install-file -Dfile=valkey-glide-1.0.0-osx-aarch_64.jar -DgroupId=io.valkey -DartifactId=valkey-glide -Dversion=1.0.0 -Dpackaging=jar -DpomFile=valkey-glide-1.0.0.pom -Dclassifier=osx-aarch_64

and for dependency:

dependencies {
    implementation group: 'io.valkey', name: 'valkey-glide', version: '1.0.0', classifier: 'osx-aarch_64'
}

[jamesward]

I'm trying that (but with linux-x86_64) and it isn't quite working in a Gradle project:

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileKotlin'.
> Could not resolve all files for configuration ':compileClasspath'.
   > Could not resolve io.valkey:valkey-glide:1.0.0.
     Required by:
         project :
      > A dependency was declared on configuration 'linux-x86_64' which is not declared in the descriptor for io.valkey:valkey-glide:1.0.0.

But actually it looks like the artifacts are now on Maven Central so hopefully this workaround isn't needed anymore. I'll try to use those artifacts now.

[jamesward]

That error was because I was specifying the classifier in the wrong way in the dependency definition with build.gradle.kts. I did:

implementation("io.valkey", "valkey-glide", "1.0.0", osdetector.classifier)

But that sets the configuration property not the classifier property. doh :(

This works:

implementation("io.valkey", "valkey-glide", "1.0.0", classifier = osdetector.classifier)

And it looks like I can just do:

implementation("io.valkey", "valkey-glide", "1.0.0")

But this might only be working for linux-x86_64 because that is the only artifact with configuration in the Gradle metadata file:
https://repo1.maven.org/maven2/io/valkey/valkey-glide/1.0.0/valkey-glide-1.0.0.module

[jamesward]

Here is the project that works for me (on linux-x86_64):
https://github.com/jamesward/hello-valkey-glide-kotlin

It'll be interesting to see if the classifier doesn't work for others on different OS / Architectures.

[Yury-Fridlyand]

I guess that gradle resolves linux-x86_64 version of the module if classifier is omitted.

[Yury-Fridlyand]

Do we need this PR? GLIDE is already published on maven central.

[sullis]

I am successfully using valkey-glide 1.0.0 in a Maven project:

https://github.com/sullis/valkey-playground/blob/main/pom.xml

I am using os-maven-plugin to get the right classifier