chore: Use ow2-nexus as the snapshot repository

[slarse]

Fix #3648

This also requires the credentials in the Jenkins Spoon-Snapshot-Deployer job to be updated with the OW2 credentials (hence titled as wip), but I think that should be all.

I'm not sure about the ID for the repository, is there some convention for that?

[monperrus]

LGTM.

Just after, we'll have to update the Jenkins deployment job. For this, could you create an account on ci.inria.fr/?

[slarse]

@monperrus I've signed up, sent a request to join the "Spoon Open Source Project". Was that the right project? :)

[monperrus]

accepted! welcome to SOS :)

[slarse]

Great, I've got access to the project, but with minimal access rights :)

[monperrus]

fixed, you're now admin. with great power...

[slarse]

with great power...

Comes great hubris! I'm having a look around now getting a feel for what's where :)

[slarse]

@monperrus Alright, I've figured out where everything is (build settings, settings.xml, credentials, etc). All I need now are the OW2 credentials. You could enter them yourself into the credentials manager (and name them something obvious), or send them to me and I'll enter them. My GPG key is over here if you want to encrypt the message.

[monperrus]

just sent you the GPG encrypted credentials over email

[slarse]

I believe that everything is now ready for the switch as far as spoon-core goes. FYI I changed the ID of the snapshot repository to ow2.org-snapshot just to clarify that it's for snapshots. Perhaps other OW2 repos are used for other things in the future.

I also noticed that spoon-visualisation/pom.xml lists maven.inria.fr-snapshot as its snapshot repository. Should I switch that over to OW2 as well? It's not deployed by the Spoon Snapshot Deployer, and I couldn't find any other job that actually deploys it, so I'm not sure if it matters.

[monperrus]

I also noticed that spoon-visualisation/pom.xml lists maven.inria.fr-snapshot as its snapshot repository. Should I switch that over to OW2 as well? yes, for sake of consistency.

[slarse]

Actually, that turned out to be something unrelated, on a closer read ("malai-public-snapshot" as opposed to "spoon-public-snapshot"). Reverted that change.

Anyway, this is ready now, but the settings.xml file in the Jenkins job must be swapped switched to the OW2 version before merge (it's a button click, everything is ready). We could coordinate the merge before or after the meeting today, or just ping me and I'll make the swap ASAP.

[slarse]

Actually, it doesn't really matter if one or two snapshot deployments fail in the meantime.

I've made the swap, merge when ready and hopefully the snapshot should deploy as planned!

[monperrus]

Thanks a lot!

[slarse]

Aaaaand, it broke.

[ERROR] Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8:deploy (injected-nexus-deploy) on project spoon-core: Failed to deploy artifacts: Could not transfer artifact fr.inria.gforge.spoon:spoon-core:jar:jar-with-dependencies:8.3.0-20201019.125525-1 from/to ow2.org-snapshot (https://repository.ow2.org/nexus/content/repositories/snapshots/): Failed to transfer file: https://repository.ow2.org/nexus/content/repositories/snapshots/fr/inria/gforge/spoon/spoon-core/8.3.0-SNAPSHOT/spoon-core-8.3.0-20201019.125525-1-jar-with-dependencies.jar. Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]

Debugging :)

[slarse]

It was a typo, the build is now fine and snapshots are being deployed to the OW2 nexus

https://repository.ow2.org/nexus/content/repositories/snapshots/fr/inria/gforge/spoon/spoon-core/8.3.0-SNAPSHOT/