-
Notifications
You must be signed in to change notification settings - Fork 264
cannot read dependency from GitHub packages #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I was missing the token to be able to read packages from GitHub packages. I created a Personal Access Token (https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token) that only has the read packages access defined. After that I changed the gradle repository definition to:
and added my username and the token as password to my ~/.gradle/gradle.properties file:
Now it works |
Oh, indeed GitHub requires a token even for read access. I've updated the |
I suppose once the client is final, it will be available via maven central? Because otherwise everyone who is using Spring Data Elasticsearch would need to create a PAT. |
Absolutely! We're working on it, as it has to be part of Elastic's "unified release process" that coordinates artifact construction and publication for all Elastic products. |
Thanks for providing this, I just wanted to do a first test. Maybe I am missing something, but I don't get the dependency, I am getting an error about not being authorized:
My setup for gradle is as in the documentation, when I try to open the link to the metada file, my browser wants me to login as well.
The text was updated successfully, but these errors were encountered: