[
https://issues.apache.org/jira/browse/LUCENE-9170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024318#comment-17024318
]
Ishan Chattopadhyaya commented on LUCENE-9170:
----------------------------------------------
My intuition is that by default ivy tries to resolve using http using maven
central, but there's some override for https maven central. Seems like these
places (in the patch) didn't receive that override.
bq. The fix just enforces the repo to use, but is this a bug in the Maven ant
tasks?
Yeah, and it feels so awkward. Is there a better fix?
> wagon-ssh Maven HTTPS issue
> ---------------------------
>
> Key: LUCENE-9170
> URL: https://issues.apache.org/jira/browse/LUCENE-9170
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Ishan Chattopadhyaya
> Assignee: Ishan Chattopadhyaya
> Priority: Blocker
> Fix For: 8.5
>
> Attachments: LUCENE-9170.patch, LUCENE-9170.patch
>
>
> When I do, from lucene/ in branch_8_4:
> ant -Dversion=8.4.2 generate-maven-artifacts
> I see that wagon-ssh is being resolved from http://repo1.maven.org/maven2
> instead of https equivalent. This is surprising to me, since I can't find the
> http URL anywhere.
> Here's my log:
> https://paste.centos.org/view/be2d3f3f
> This is a critical issue since releases won't work without this.
--
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
