@lhotari Much appreciated.

I tested locally building the Central Portal Publish API zip file with the nmcpZipAggregation task for debugging the nmcp plugin.

# create a zip file for NMCP aggregation with signing
ORG_GRADLE_PROJECT_signingKey=$(gpg --armor --export-secret-keys 1234578) \
ORG_GRADLE_PROJECT_signingPassword=my_key_password \
ORG_GRADLE_PROJECT_sonatypeUsername=example_username \
ORG_GRADLE_PROJECT_sonatypePassword=example_password \
CI=1 \
./gradlew -Pversion=1.6.1 nmcpZipAggregation

# and then checked the build/nmcp/zip/aggregation.zip file
unzip -v build/nmcp/zip/aggregation.zip |less

The result looks fine.

One detail which might have to be revisited since the last time Maven Central publishing was used is creating a token for the Portal Publish API. This is mentioned in the documentation.

To generate a user token, visit the Account page and click the "Generate User Token" button.

@lhotari

One detail which might have to be revisited since the last time Maven Central publishing was used is creating a token for the Portal Publish API. This is mentioned in the documentation.

It should be already setup with secrets:

MAVEN_PASSWORD, MAVEN_USER

E.g., the JavaFastPFor project, uses these same tokens, so they work.

I try merging this PR and testing it out and it failed even after I tried many things.

So I am declaring it a dead-end.

I try merging this PR and testing it out and it failed even after I tried many things.

So I am declaring it a dead-end.

I added a comment about what went wrong in one of the last attempts: 96d851c#r177629944 .
It's pretty painful to get things right. I'll try to find time for a follow up so that we could be successful next time.

hey @lemire @lhotari i see this PR was merged to master but i dont see it in the commits, https://github.com/RoaringBitmap/RoaringBitmap/commits/master/
was it reverted?

I'm happy to help with getting this working

@lhotari @kevinjqliu It cannot work because one workflow using GITHUB_TOKEN cannot trigger the other workflows. So it was dead on arrival.