> I ended up cheating a bit and using the 8.11 Ant build to upload the
> Maven artifacts to Nexus before I saw Dawid's message.
If ant can do it then it surely can be ported to gradle though -
perhaps worth exploring as well? If you create an issue I'll take a
look,
although I admit it's low on
I ended up cheating a bit and using the 8.11 Ant build to upload the
Maven artifacts to Nexus before I saw Dawid's message.
The bundle idea looks like a promising path to use for upcoming
releases. Since we require logging into Nexus anyway for promotion, it
doesn't make things worse to also do
Hmm do the RC builds have an RC1,RC2,etc notation in the version so one can
tell which one is running? (and if you've really restarted to the intended
version etc when testing/comparing them)? if so we'd be rebuilding anyway
to get rid of it?
On Mon, Dec 6, 2021 at 10:41 AM Dawid Weiss wrote:
>
> 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
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?
On Mon, Dec 6, 2021 at 9:15 AM Dawid Weiss wrote:
> Hi Adrien,
>
> So. From
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
There may be some loose ends here. See
https://issues.apache.org/jira/browse/LUCENE-9809?focusedCommentId=17433373=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17433373
as a starting point for gradle command.
Related:LUCENE-10174, Umbrella: LUCENE-9488
So
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
\
> Using Lucene 9 with the module system should be considered
> experimental. We expect to make progress on this in future 9.x
> releases.
Experimental seems consistent with what the changelog says. I honestly
don't think many people are using the
module system for production purposes so it's a
It's been >72h since the vote was initiated and the result is:
+1 11 (10 binding)
0 1
-1 0
This vote has PASSED.
On Mon, Dec 6, 2021 at 10:15 AM Adrien Grand wrote:
>
> Thanks Uwe for finding this issue. I agree with your and Tomoko's
> judgement that it doesn't need to be a blocker for
Thanks Uwe for finding this issue. I agree with your and Tomoko's
judgement that it doesn't need to be a blocker for this release
candidate.
Tomoko's suggestion to add a note to the release announcement sounds
like a good idea to me. I added the following note at
11 matches
Mail list logo
