[
https://issues.apache.org/jira/browse/LUCENE-9809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433605#comment-17433605
]
Dawid Weiss commented on LUCENE-9809:
-------------------------------------
mavenToApacheReleases already checks that it's a non-snapshot release (because
nexus wouldn't accept it). I wonder if the hash check should be done in the
python script instead of the gradle build... But up to you, really.
I'm used to releases which do both things in one step - collect distribution
artifacts locally and push jars to nexus (something like a release thask that
depends on both assembleRelease and mavenToApacheReleases) - then consistency
is less of a problem.
> Adapt Release Wizard to only release Lucene
> -------------------------------------------
>
> Key: LUCENE-9809
> URL: https://issues.apache.org/jira/browse/LUCENE-9809
> Project: Lucene - Core
> Issue Type: Sub-task
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Fix For: main (9.0)
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
