[GitHub] [lucene] HoustonPutman commented on pull request #523: LUCENE-10293: adds a stand-alone prepareSonatypeBundle that compiles …

[GitBox <gi...@apache.org>]

HoustonPutman commented on PR #523:
URL: https://github.com/apache/lucene/pull/523#issuecomment-1098274229

   Hey @dweiss I am finishing up the Solr 9.0.0 release and ran into this issue.
   
   It looks like both Lucene 9.0 and 9.1 used the ant command from 8.11 to do the maven upload.
   
   I tried using this method but unfortunately when you do the "upload bundle" there's a bug where it will add additional folder levels to the artifacts that you are uploading (if you have multiple artifacts included). I tried all possible ways I could think of around this, but nothing resulted in a correct repository.
   
   After lots of looking, I found out that Spark has completely automated this part of their build: https://github.com/apache/spark/blob/v3.2.1/dev/create-release/release-build.sh
   
   So I am building a script and releaseWizard entry to do this for Solr. Will happily port it to lucene afterwards.
   
   Quick question though, do you think we should create the staging repository as a part of the release candidate, then delete it/promote it if the vote succeeds? If we did that, then we wouldn't have to add the maven artifacts to the release-candidate dist folder, and users could access the maven artifacts in a more natural way. I haven't used the staging repositories myself before, so I'm not sure if this is a good idea or not.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org