> I believe maven/nexus natively allows publishing an RC to the staging repo > and then manually promoting to a release. Apache infra has this dual set up > for us already. > Would gradle be able to hook into that process?
If it's the same as other open source Nexus installations then the "staging repository" is an intermediate step that's always there - there is no way to publish directly to releases. The question is how do you upload to the staging repository - it's one of the methods I mentioned in my previous e-mail. D. > > On Mon, Dec 6, 2021 at 9:15 AM Dawid Weiss <dawid.we...@gmail.com> wrote: >> >> Hi Adrien, >> >> So. From gradle's point of view I don't think it's possible to reuse >> exactly the same files as were present in the RC candidate. >> Technically artifacts are a result of the build (tasks) - they can't >> be taken arbitrarily from disk. Or rather: it may be possible but will >> require terrible hacks. >> >> I suggested to Jan that we could instead package the artifacts as >> Sonatype Nexus's "distribution bundle" - a ZIP file with all the >> information (poms, checksums, jars) that should be staged. This >> requires a manual upload of this ZIP file but otherwise allows >> publishing exact identical files that were part of the RC. >> >> If we only care about releasing from the same git hash (but with >> rebuilt artifacts - so some things in manifests may change!) then >> indeed it's doable via the command Jan mentioned. >> >> I don't think there exists a third way of doing this (?). >> >> I can help add a task that will assemble a Sonatype Nexus bundle which >> you'll be able to download to Nexus. It should ultimately be part of >> the release candidate artifacts - this would make it explicit what >> will get uploaded. >> >> Dawid >> >> On Mon, Dec 6, 2021 at 2:19 PM Adrien Grand <jpou...@gmail.com> wrote: >> > >> > Hello, >> > >> > The release wizard still suggests using Ant for Maven publication: >> > >> > cd ~/.lucene-releases/9.0.0/lucene >> > ant clean stage-maven-artifacts \ >> > >> > -Dmaven.dist.dir=~/.lucene-releases/9.0.0/RC4/dist/lucene-9.0.0-RC4-rev-0b18b3b965cedaf5eb129aa41243a44c83ca826d/lucene/maven >> > \ >> > -Dm2.repository.id=apache.releases.https \ >> > >> > -Dm2.repository.url=https://repository.apache.org/service/local/staging/deploy/maven2 >> > >> > The Gradle build has a `mavenToApacheReleases` task that seems to do >> > what I want, but I can't find how to tell it to use the JARs of RC4 >> > rather than those produced by `gradlew assembleRelease`. Can someone >> > help me with this? >> > >> > -- >> > Adrien >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> > For additional commands, e-mail: dev-h...@lucene.apache.org >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: dev-h...@lucene.apache.org >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
