[
https://issues.apache.org/jira/browse/LUCENE-9809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433373#comment-17433373
]
Jan Høydahl commented on LUCENE-9809:
-------------------------------------
ReleaseWizard step 6.4 uses Ant command
{code:java}
In the source checkout do the following (note that this step will prompt you
for your Apache LDAP credentials) cd ~/.lucene-releases/9.0.0/lucene
ant clean stage-maven-artifacts \
-Dmaven.dist.dir=~/.lucene-releases/9.0.0/RC1/dist/lucene-9.0.0-RC1-rev2719cf6630eb2bd7cb37d0e8462dc912d8fafd83/lucene/maven
\
-Dm2.repository.id=apache.releases.https \
-Dm2.repository.url=https://repository.apache.org/service/local/staging/deploy/maven2
{code}
The gradle equivalent is
{code:java}
./gradlew mavenToApacheReleases -Dversion.release=<ver>
-PasfNexusUsername=<user> -PasfNexusPassword=<passwd>{code}
While the ant task prompted for ASF user/pass, the gradle equivalent expects
these as cli args, or as env.vars {{ASF_NEXUS_USERNAME}} and
{{ASF_NEXUS_PASSWORD}}. There does not seem to be any configuration for
specifying the folder where the signed and voted upon artifacts reside.
[~dweiss] will the command instead use the last build's build folder? We likely
need the wizard to prompt for user/pass, and somehow issue the command with the
env vars set, without revealing the password in logs in plaintext. Going to
check...
> 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
