moving hosting of artifacts out of jcenter (to maven central)

EOL of bintray/jcenter is planned for 2021/05/01 as explained in Service End for Bintray, JCenter, GoCenter, and ChartCenter | JFrog.

Proposed plan to move the release artifact out of bintray:

• Prepare hosting on maven central (via OSS sonatype), (see OSSRH Guide)
  • create user account for release manager on https://issues.sonatype.org/
  • request groupId org.jmonkeyengine project on oss.sonatype see Producers:
    • create a ticket on OSSRH
      • summary : hosting of org.jmonkeyengine
      • description: Request to host artifacts from jMonkeyEngine, currently hosted on bintray/jcenter (but not yet sync)
      • groupId: org.jmonkeyengine
      • project Url: https://jmonkeyengine.org/
      • scm: https://github.com/jMonkeyEngine/jmonkeyengine.git
      • usernames: add davidb (to be able to sync from bintray) and user account previously created
      • already synced : None
    • create a TXT record in your DNS referencing your OSSRH ticket number and your groupId will be approved on OSSRH
• request maven central sync on bintray (via the old bintray UI)
  • eg: https://bintray.com/jmonkeyengine/org.jmonkeyengine/jme3-core/#central
  • if existing artifacts don’t match the requirements, sync will failed
• update release workflow
  • replace into scripts deploy release to bintray by deploy release to oss.sonatype (see deploy via Gradle )
  • update doc for release manager
• update documentation about repository where are hosted artifacts (README, wiki,…)
• update dependencies of artifact that depend on jmonkeyengine

[davidB]

jme3-core 3.3.2-stable is sync from bintray to maven central (see https://repo1.maven.org/maven2/org/jmonkeyengine/jme3-core/) Every artifacts and version will require manual sync. 😦 I can do it for version 3.3.2-stable if you like. @stephengold can you try to sync some, use your ossrh cred as token (key == username, password == password) ?

[stephengold]

Apparently jme3-vr didn’t exist in JME 3.1.0. Other than that, the automation worked flawlessly, even for jme3-android. I didn’t have to do anything manually.

What happened regarding linking jme3-ios to JCenter?

I’ll try to copy the remaining “stable” releases tomorrow (3.2.0, 3.2.1, 3.2.2, and 3.2.3).