-
Notifications
You must be signed in to change notification settings - Fork 21
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
Maven central #35
Comments
What keeps me away from maven central is:
Anyway, if you want to embark in this quest, be my guest :)
Ps: I thought the solution to #19 was enough the |
So, yes. There are additional credentials, but that is imho no issue. local publishing is fine or put it up as a ci/cd variable. publishing on gradle is easy (see my build.gradle). But credentials are super easy to aquire, you just have to open an issue on their jira (sonartype). Fully automatic.
Yes. There is a snapshot repository. And for the releases: How often are you modifying them? Me: never
You can add the release repository (
oh. Looked different, but checked the pom.
Yes, it pretty much is easy but not adding a repository is easier, especially if you project wants to make reproducible builds. |
Sorry but I continue to prefer my solution, especially for the time, I can publish in ~10s and it's available literally right away to being fetch as a dependency for consumers This being said, I do recognise the value of being on maven central, I'm not stopping you at all. If you want, you can go ahead. |
Okay, I'll register No clue how you can publish there then, but my username will have access, I can subscripe to mary and then upload the builds. Hope that works well. Or self building is better, I can only publish in that namespace. |
I'd expect that multiple people might be able to publish, I guess in big organizations is like that, or? Anyway, in case that's not possible, it's not a big deal, you can publish there We will find some confy solution on the long run |
Sure, you can publish. You just need an account on their jira. https://issues.sonatype.org/secure/Signup!default.jspa Instructions at https://central.sonatype.org/publish/publish-guide/ To confirm the group, can you create repository https://github.com/kotlin-graphics/OSSRH-92155? |
I'll look into it when I get a moment, but I don't see anytime soon unfortunately Repo create: https://github.com/kotlin-graphics/OSSRH-92155 |
Permission granted (https://issues.sonatype.org/projects/OSSRH/issues/OSSRH-92155), thanks! You can remove the repository again, I will publish probably tomorrow (went on the Krottenkopf today, quite tired) If you decide to also publish on maven central, either ask me to add you (requires human interaction I guess) or do a "New Project" request. |
So, the plan for releasing is....not really present :) Following possiblities:
More questions:
And I can't just publish glm, I gotta publish it with all dependencies (kool and unsigned afaik). Maybe publishing other (even more popular) artifacts like dear imgui is a good idea. Lot of work :) |
It should be easy, theoretically it should be enough to just specify the given group in the publication
Really? I'll add you over there as well then |
Easy, can you release a test build? |
What's the best way to do that? I mean, can I release, test and delete it? |
I mean, just release a build :) |
How about publishing the library to maven central? With all dependencies?
2 more things that go in that direction:
Might even be the magic solution to #19
The text was updated successfully, but these errors were encountered: