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

[davidB]

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]

I can take care of some of the steps (on bintray and OSSRH, but not on DNS).

[stephengold]

Thank you for opening this issue and outlining the plan. FYI there is also a discussion topic at the JMonkeyEngine forum/hub:
https://hub.jmonkeyengine.org/t/sunset-on-may-1st-bintray-jcenter/44251

[stephengold]

What does "readme doc on" entail?

[riccardobl]

Thank you for opening the issue.
I've also started doing some migrations as reported here: https://hub.jmonkeyengine.org/t/sunset-on-may-1st-bintray-jcenter/44251/36?u=riccardoblb
Regarding the DNS changes, i can do them, i just need to know what to do in case someone else is taking care of the process.

[davidB]

I created the request for org.jmonkeyengine on OSSRH: [OSSRH-64318] hosting of org.jmonkeyengine - Sonatype JIRA with @stephengold and @davidB as release manager.
Adding other "release manager" and gpg key could be done later (I did it for one of my hosted artifact), iirc they prefere to register key for individual than a generic key (like suggested on the forum). It will also be possible to remove my account as release manager.

@riccardobl can you add a TXT record on DNS for org.jmonkeyengine with value OSSRH-64318 ?

[MeFisto94]

One question: Do we get troubles as our packages used to be com.jme3.x?
I mean the artifact coords are org.jmonkeyengine, but the whole code actually isn't.
And we have no control over jme3.com, do we?

[davidB]

One question: Do we get troubles as our packages used to be com.jme3.x?
I mean the artifact coords are org.jmonkeyengine, but the whole code actually isn't.
And we have no control over jme3.com, do we?

No troubles, I guess. I host artifact under groupId net.alchim31.maven, but the java packages are not under net.alchim31 see https://github.com/davidB/scala-maven-plugin/tree/master/src/main/java

What does "readme doc on" entail?

I mean to udpate the README,... if they have reference to the repository from where to download artifacts

[riccardobl]

@riccardobl can you add a TXT record on DNS for org.jmonkeyengine with value OSSRH-64318 ?

For jmonkeyengine.org or for org.jmonkeyengine.jmonkeyengine.org ? I added this one:

[pspeed42]

Maven central doesn't care about package names. When you reserver a groupId, they need some assurance that someone who actually owns the domain isn't going to come along tomorrow and claim it.

No pom.xml with com.jme3 as a groupId is a real release. If these exist then we need to let them die.

[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) ?

[pspeed42]

@davidB super cool. I'm wondering if there are any tips you can provide the community for anyone also trying to move their libraries over? Any pitfalls that we should watch out for, etc.? (I have quite a few libraries to move myself and so have a vested interest.)

[stephengold]

@davidB I'll try doing some manual syncs and report back here.

[stephengold]

I tried syncing jme3-android v3.3.2-stable from Bintray, using my OSSRH username ("stephengold") and password, and I got "Authentication failed". I also tried syncing jme3-core v3.3.0-beta2 in the same manner and got the same result.

[davidB]

@pspeed42 yes I could provide a small instructions list to move, when we have a working flow.

@stephengold have you already try to connect/sign-in to https://oss.sonatype.org/ ? if you connect and retry to sync, if failed to authenticate, you can try with the access token provide at https://oss.sonatype.org/#profile;User%20Token (click on you name on top right > profile > User token (in the combobox) )

EDIT: you can also set the OSS sonatype info value into your Account section https://bintray.com/profile/edit

[stephengold]

I'm signed into Sonatype. Thanks for explaining how to generate a user token. I tried using that token to sync jme3-android v3.3.2-stable. This time I got a 403 error: "User 'stephengold' missing 'stage' permission for staging profile: 13769b099076e"