[stage-vote-release-plugin] Execution failed for task ':releaseRepository' due to missing nexus.txt file

[vlsi]

[stage-vote-release-plugin] Execution failed for task ':releaseRepository' due to missing nexus.txt file

[zabetak]

At the moment, I am trying to see if there is a graceful way to recover and continue with the publishDist task. Simply adding the missing nexus.txt in the appropriate place and re-running ./gradlew publishDist will not work cause it will fail trying to move/cp the svn artifacts.

[zabetak]

Finally, I decided to manually perform the remaining steps (hopefully I didn't miss anything):

1. Login to https://repository.apache.org/
2. Select the staging repository mentioned in the VOTE email thread:orgapachecalcite-1200
3. Click release (and check drop as well)
4. Checkout the main branch: git checkout main
5. Merge the current release candidate to main: git merge calcite-1.34.0-rc0
6. Push the main branch to the ASF remote: git push origin main
7. Create a tag without rc suffix: git tag -a calcite-1.34.0 7dfd641baeb0e1b26dec04da5241c3999fe0ac6a -m "Tag explicitly 1.34.0 release without -rc suffix"
8. Push the new tag to ASF remote: git push origin calcite-1.34.0

[vlsi]

The best way to handle this would be using Nexus server itself for associating "release candidates" with "staging repositories".

I did try contributing the feature to gradle-nexus/publish-plugin, unfortunately, the authors were not responsive: gradle-nexus/publish-plugin#145

[zabetak]

According to the comments there some part of the change was merged in gradle-nexus/publish-plugin#201
Do you think that we could build on top of that or we are missing more things?

[vlsi]

They went with a separate FindStagingRepository task rather than teaching the existing InitializeStagingRepository task to lookup the repository.

Apparently, if initializeStagingRepository was able to do both "find if exists" and "create if missing", then it would be way easier to use.

It might be something like #41 + findStagingRepository would do the trick, however, I'm not willing to spend more time time on reverse-engineering GNPP code.

nexus.txt is not a pressing issue for me at the moment, and I'm balancing between:

• Forking GN-PP
• Working on something else