You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/03/12 11:58:00 UTC

[jira] [Commented] (LUCENE-9836) Fix 8.x Maven to work with Maven Central again

    [ https://issues.apache.org/jira/browse/LUCENE-9836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17300257#comment-17300257 ] 

ASF subversion and git services commented on LUCENE-9836:
---------------------------------------------------------

Commit c2d5f410e51678dcc6b538b303f054c41189aa1f in lucene-solr's branch refs/heads/branch_8x from Uwe Schindler
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=c2d5f41 ]

LUCENE-9836: Remove ant run-maven-build (won't bootstrap anymore), fix more places where the secured Maven Central repo is needed to execute


> Fix 8.x Maven to work with Maven Central again
> ----------------------------------------------
>
>                 Key: LUCENE-9836
>                 URL: https://issues.apache.org/jira/browse/LUCENE-9836
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Uwe Schindler
>            Priority: Major
>
> Currenty the Maven related stuff in 8.x completely fails, because Maven-Ant-Tasks is so outdated, that it has hardcoded Maven Central without HTTPS. This makes downloading fail.
> You can mostly fix this with an additional remote repository, so it can fallback to that one.
> I'd like to do the following on 8.x:
> - Remove the Ant-Support for Maven: {{ant run-maven-build}} (this no longer bootsraps, because Maven Ant Tasks can't download Maven, as here is no way to override hardcoded repo; I have a workaround in forbiddenapis, but that's too complicated, so I will simply remoe that task)
> - Fix the dependency checker: This works, but unfortunately there are some artifacts which itsself have "http:" in their POM file, those fail to download. Newer Maven versions have an hardcoded "fixer" in it, but Maven Ant Tasks again is missing this. I have no idea how to handle that.
> I already tried some heavy committing, but the only way to solve this is to replace maven-ant-tasks with the followup ant task. I am not sure if this worth the trouble!
> What do others think? Should we maybe simply disable the Maven Dependency checker?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org