[
https://issues.apache.org/jira/browse/LUCENE-9488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17425178#comment-17425178
]
Dawid Weiss commented on LUCENE-9488:
-------------------------------------
Hi Jan. I've added collecting changes and maven artifacts... see the commits
here:
https://github.com/apache/lucene/pull/359
But... it's all looking rather badly to me. I'd rather clean it up properly
before we make the 9.0.0 release. I mean: it's a shiny new major version so
maybe we should have the release process upgraded too? If you don't mind
waiting a few days and working with me, I'll be glad to help.
Anyway, if you'd like to try out the PR, please do - gradlew assembleDist will
collect everything in that 'distributions' folder (and this is wrong too... but
let's leave with it for now). You may have to set up gpg signing in your
~/.gradle/gradle.properties:
{code}
signing.keyId=
signing.password=
signing.secretKeyRingFile=
{code}
If you're running with an agent, the password can be blank.
The thing I couldn't get past is Nexus. In theory, this should upload artifacts
to staging:
{code}
gradlew publishJarsPublicationToApacheReleasesRepository -PasfNexusUsername=
-PasfNexusPassword=
{code}
I can log in to repository.apache.org and I see the releases/staging repository
but I can't upload anything:
{code}
Could not PUT
'https://repository.apache.org/content/repositories/releases/org/apache/lucene/lucene-classification/9.0.0-SNAPSHOT/maven-metadata.xml'.
Received status code 400 from server: Bad Request
{code}
I'm not sure whether it's insufficient karma or something else. I looked at the
ant build but I don't see anything special there... Can you try and see if you
can upload anything to the staging environment via gradle?
An alternative to having gradle upload artifacts to Nexus directly would be to
prepare a "nexus release bundle" (ZIP with all the artifacts and metadata
inside) which you can then upload in Nexus's user interface... This would have
the benefit that all the "release" binaries would indeed be prepared in a
single location - binaries, sources and Maven artifacts.
> Update release process to work with Gradle.
> -------------------------------------------
>
> Key: LUCENE-9488
> URL: https://issues.apache.org/jira/browse/LUCENE-9488
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
> Reporter: Erick Erickson
> Assignee: Mike Drob
> Priority: Major
> Attachments: Skjermbilde 2021-10-05 kl. 11.18.28.png
>
> Time Spent: 16h 20m
> Remaining Estimate: 0h
>
> The release process needs to reflect using Gradle rather than Ant. I suspect
> this will be a significant task, thus it has its own JIRA
--
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
