I'm maintaining the OSS library RxJava and up until today, we were able to release versions of it through bintray which were also synced to maven properly. The last successful sync was on February 25.
Today, the CI release failed with 403 forbidded and quoting
To be synced to Maven Central your package needs to be included in the JCenter repository.
When I visited the bintray page of the project, it seems there is no link to JCenter there indeed. The neighboring ReactiveX libraries (such as RxKotlin) have this link. I can't remember if we had this link before or not.
Is it possible the link was somehow severed or there was a recent change that mandates JCenter linkage?
It seems that there was an issue that was resolved by the Bintray team developers.
Your packages are now linked and available for download via Jcenter.
We apologize for the inconvenience.
JFrog team.
Related
I have a library shared in JCenter, which I post to through Bintray.
Recently, it is announced JCenter and Bintray are sunsetting, and many advised us to go to MavenCentral. I'm looking to move migrate it over.
Then I notice within the Bintray, it is stated my library is on Maven too, and the user can get my library using
maven {
url "https://dl.bintray.com/elye-project/maven"
}
So I'm confused, does that means I am already in Maven? Is this is just another name for JCenter and will not be available as well?
As I read more, I found an article stating we can publish our library from Bintray to MavenCentral too.
I also read if I need to submit my library to MavenCentral, I need to first create an issue in Sonatype.
Then I saw Sonatype is actually having Nexus Repository Manager. Then I find OSSRH uses Nexus Repository Manager.
I am super confused about what these terms are, and how are they related?
Bintray, JCenter, Maven, MavenCentral, OSSRH, Sonatype, Nexus.
Can someone give a brief description about them, and help to connect the dot for me?
MavenCentral is the place where Java open source artifacts should be published
JCenter was such a place.
Maven is a build system, not a repository. Many repositories have Maven format, which makes them readable from Maven and Gradle.
Sonatype Nexus and JFrog Artifactory are repository managers. You can install them to manage internal and external artifacts on your own server, which is advisable inside a company.
The Byteman website advertises version 4.0.11 as released: https://byteman.jboss.org/downloads.html
But only some artifact IDs are available on Maven Central: https://search.maven.org/search?q=g:org.jboss.byteman
Did something go wrong during the release? Did artifact IDs change?
Thanks for reporting this. There was no problem reported during the maven build or upload to the Sonatype repo and my release of the artefacts was indicated as successful. However, Sonatype has been rather flaky recently. It seems to have lost many of the artefacts at release (before transfer to Maven Central).
I have hand uploaded all the missing artefacts for 4.0.11 to Sonatype and checked that they are all currently resident in their repo. I also checked and the 3.0.18 artefacts (originally released at the same time) also seem to be present on their site. These all ought to get pushed over to Maven Central soon. If that doesn't happen within a day or two (worst case) then that probably means the Sonatype copying operation is wedged again. Let me know if so and I will raise the transfer problem with them. Let's keep our finger crossed they don't lose the uploads.
Yarg library https://bintray.com/cuba-platform/main/yarg is linked to JCenter repository. When I try to check JCenter storage: https://jcenter.bintray.com/com/haulmont/yarg/yarg/ There are only old versions from Maven Central. Why does JCenter includes them?.
Why do new versions are not synced to JCenter? It seems that the new package is conflicting with these old packages.
Thank you for putting this into our attention.
With regards to the issue you describe, we have managed to find the root cause for it.
There was a sync issue between Bintray and JCenter after approving the package to JCenter. Since that, new packages could not sync.
We hope this clarifies and resolves your enquiry.
Please let us know if you have any follow up questions.
Yonatan Brand,
JFrog Support.
I have published a small library to Maven Central (it can be downloaded via web UI here). This was done more than a full day ago.
My understanding is that JCenter mirrors Maven Central, but for some reason I cannot find my artifact in JCenter both via web interface and as part of Maven build.
Do I need to take some action to make it appear in JCenter too?
Basically, if you want to make sure that your library will exist in JCenter, you can upload your library to Bintray under Maven repository, and request to add it to JCenter.
Bintray can also save you the trouble of uploading your library to Maven Central, and do it for you.
Enjoy
Two weeks later the artifact is now visible in JCenter. Apparently it just takes some time to appear there.
An old legacy project in my team is being salvaged for any usable part, one of its dependency is play-json_2.10 with a version number 2.2. However since its too old, its missing from all the major repository, including typesafe and sonatype central. The only place i can find it is on github:
https://github.com/mandubian/play-json-alone
I could download it and manually save it to a local maven repo but my team mate won't be able to see it after checking out my commit. Is there a way to make maven downloading from github and put source code somewhere? Thanks a lot.