Page Comparison

...

Info
This guide is only intended for use when there are issues with package syncing that need to be manually resolved. The Linux Foundation release automation should perform this step automatically by using the Bintray API.

Step-by-step guide

Navigate to your Bintray repository
Switch to the Old UI by clicking 'Go to Old Look' in the top navigation bar.
Click on the package you'd like to sync.
Ensure the package has been include in JCenter.
There will be a 'JCenter' logo in the bottom right of the package detail view if the package has been included.
Click on the 'Maven Central' tab in the package detail view.
Ensure the 'Close and release repository when done' option is checked, and click 'Sync'
If successful the Last Sync Status on right-hand side will display: "Successfully synced and closed repo."

If unsuccessful, you'll need to resolve the issues stated in the Last Sync Status. These may be:

Missing Source Jars
Your package needs to include a sources.jar in order be included in Maven-Central. Recreate your package with sources, redistribute the package to Bintray, and attempt to sync again.
Missing: no javadoc jar found in folder '<package path / version>', Dropping existing partial staging repository.
Your package needs to include Javadocs in order be synced out to Maven Central. Add these, redistribute the package to Bintray, and run the sync again.
Failed to promote repository: <repository name>. Server response: ... <msg>Unhandled: Staging repository is already transitioning: ...<\msg> ... Dropping existing partial staging repository.
Only one package can be released at a time. Once the current one complete, or after waiting a couple of minutes, syncing the repository again should succeed.

If there are other undocumented issues, retrying after a few minutes will generally be all that is needed to sync artifacts successfully.

Info
Repositories managed by The Linux Foundation should be pre-enabled to use Bintray's signing key for package uploads. If that is not the case another error message stating the package has not been signed will be displayed. If this happens please contact support.linuxfoundation.org to get the repository reconfigured and redistribute your artifacts.