I remember another proposal which consisted of using the Gradle build to rebuild Maven artifacts at the type of uploading to Nexus, which I liked less because it involved re-building, and who knows what may happen that could produce slightly different binaries. I like your new proposal better.
> Those are browsable and artifacts can be downloaded from there before voting (although I'm not sure if anybody inspects those maven artifacts) I suspect you know this, but the smoke tester does download these artifacts and runs some checks. On Thu, Nov 17, 2022 at 2:31 PM Dawid Weiss <dawid.we...@gmail.com> wrote: > > Yeah, I thought so. I'd love to help improve this as part of the next > release - it should really be simple. I know the old way was to have maven > artifacts separately (to agree/vote upon) but in my opinion it wouldn't > change much if the release manager pointed to release artifacts + maven > artifact (staging) repository uploaded to Apache Nexus. Those are browsable > and artifacts can be downloaded from there before voting (although I'm not > sure if anybody inspects those maven artifacts). Also, the staging > repository can "hang" unreleased until the voting is closed. This would > make the build side of things much easier and wound't require any extra > infrastructure/ steps. > > Dawid > > On Thu, Nov 17, 2022 at 2:08 PM Adrien Grand <jpou...@gmail.com> wrote: > >> I remember using a 8.x build to do that for the 9.0 release. >> >> On Thu, Nov 17, 2022 at 1:54 PM Dawid Weiss <dawid.we...@gmail.com> >> wrote: >> >>> >>> I looked at an old issue related to maven artifact publishing and I >>> noticed the release wizard still gives instructions to use the ant-based >>> script (which isn't there anymore?): >>> >>> ant clean stage-maven-artifacts >>> >>> I'm sorry to ask but how did release managers stage maven artifacts so >>> far on 9x? >>> >>> Dawid >>> >> >> >> -- >> Adrien >> > -- Adrien
