[
https://issues.apache.org/jira/browse/LUCENE-9836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17342663#comment-17342663
]
Uwe Schindler commented on LUCENE-9836:
---------------------------------------
Background information:
{quote}
i figured this out. Due to my change the aggregator for analysis missed the
marker "do not deploy":
https://github.com/apache/lucene-solr/commit/7521cbae963241d32083705054a2f2d41ed92053#diff-f1048c934461d61e8a7de3278b54021493da55cb4d2901155f2799929a3561b3L44
It was accidentally removed. I was not aware that smoke tester checks this. I
will check again and fix this. The other one is the Solr contrib aggregator, it
has same issue.
{quote}
All build plugins in the Maven files were removed, because the Maven POMs are
now only metadata POMs without any build logic (same like in gradle).
Smoketester then figured out that there is a POM input file which does not
appear in the deployed artifacts. So it detected the obsolete file.
The aggregator POMs were only needed for the Maven-based build, but for pure
"metadata POMs" it's useless. They are not referred anywhere, so I simply
deleted them.
Technically, we can also remove the XPath logic to detect they skipped deploy
plugin from smoke tester. We should do this anyways for main branch.
> 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
