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

David Smiley commented on LUCENE-9836:
--------------------------------------

Is there any chance this is related to the smokerelease failure:
Missing artifact 
/home/jenkins/jenkins-slave/workspace/Lucene/Lucene-Solr-SmokeRelease-8.x/lucene/build/smokeTestRelease/tmp/maven/org/apache/lucene/lucene-analysis-modules-aggregator/8.9.0/lucene-analysis-modules-aggregator-8.9.0.pom
 ?
Hossman suggested this maybe in an email March 18th in response to a 
smokerelease failure.  I saw the same failure today:
https://ci-builds.apache.org/job/Lucene/job/Lucene-Solr-SmokeRelease-8.x/ 
(#199).  Last 5 smoke tests fail.  Last passed March 15th, immediately prior to 
the last commit here. 

> Fix 8.x Maven Validation and publication to work with Maven Central and HTTPS 
> again; remove pure Maven build (did not work anymore)
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-9836
>                 URL: https://issues.apache.org/jira/browse/LUCENE-9836
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: general/build
>    Affects Versions: 8.x, 8.9
>            Reporter: Uwe Schindler
>            Assignee: Uwe Schindler
>            Priority: Major
>             Fix For: 8.x, 8.9
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to