[
https://issues.apache.org/jira/browse/LUCENE-9548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203839#comment-17203839
]
Dawid Weiss commented on LUCENE-9548:
-------------------------------------
If you take a look at the PR, Uwe, you'll see credentials are passed as
properties to the authenticator. Gradle doesn't read maven setting files but
it's groovy so you could implement any required logic in the build script.
The command in the above comment (automatically generated by convention) will
work. I think we can add a shorter alias task (that depends on the above) but
it can come later. Jenkins configs can also come later. I'd try to publish a
snapshot from local machine first to see that it works and then decide how to
solve CI configs.
> Publish master (9.x) snapshots to https://repository.apache.org
> ---------------------------------------------------------------
>
> Key: LUCENE-9548
> URL: https://issues.apache.org/jira/browse/LUCENE-9548
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Dawid Weiss
> Assignee: Dawid Weiss
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We should start publishing snapshot JARs to Apache repositories. I'm not sure
> how to set it all up with gradle but maybe there are other Apache projects
> that use gradle and we could peek at their config? Mostly it's about signing
> artifacts (how to pass credentials for signing) and setting up Nexus
> deployment repository.
--
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
