Skip to content
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

[Q] - Dependency not found on Maven #33

Open
anderson-visma opened this issue Feb 9, 2024 · 5 comments
Open

[Q] - Dependency not found on Maven #33

anderson-visma opened this issue Feb 9, 2024 · 5 comments
Assignees
Labels
question Further information is requested

Comments

@anderson-visma
Copy link

Hi, I did not find the dependency on the public maven repository I need this to add to my Android project. Note that the person Id project number is available and is been used in my current project as a gradle dependency

@anderson-visma anderson-visma added the question Further information is requested label Feb 9, 2024
@Johannestegner
Copy link
Member

Hi there!

You are correct, we have not yet added the project to the official maven repository. I will try to get it up there asap.

Will update you here and close this issue when the package is up!

@Johannestegner Johannestegner self-assigned this Feb 20, 2024
@adrsolheim
Copy link

Any update on this?

@Johannestegner
Copy link
Member

Hi!

I've been trying to get this to work, but due to lack of time, I have not succeeded yet.
It would be quite an easy task if we could replicate the way we do it on the personnummer package, but seeing we had no namespace on the s01.oss.sonatype.org service we have to use the new OSSRH way of publishing.

Building and signing the package is quite easy to do, but as of right now, there is no official plugin to upload and publish to OSSRH with gradle (only maven).

So, what I've been trying is to figure out if we should use one of the non-official plugins for automatic uploads to OSSRH, if we should go over to maven and publish with the official maven plugin or even manually upload everything until the gradle plugin is available.
I have set up a namespace (and validated it) on the new central repository page (OSSRH), and will see if I can manually upload a first package. If I can figure out how to do that, I would think that having a manual release process for the package until the official gradle plugin is done should be an OK way to go.

@netfalo
Copy link

netfalo commented Oct 1, 2024

Hej!

Is there any update on this?

@Johannestegner
Copy link
Member

Hi @netfalo , very sorry for slow response, have had some private dealings which have taken up most of my time outside of work, so have not been paying much attention to github for the last few weeks.

I've seen that the new upload procedure actually seem to have a gradle tool now, which is great, so I'll try get this up and running for both packages this weekend.

I'll let you know as soon as it's done and working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants