[
https://issues.apache.org/jira/browse/LUCENE-9836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301815#comment-17301815
]
Uwe Schindler commented on LUCENE-9836:
---------------------------------------
Hi Dawid,
we can't completely remove the POM files, but yes: I'd like to get rid of the
"separate build". I will strip down all POM files to only have metadata and
dependency information (also removing the broken test-jars which are not
created by the ANT build -- only needed by the POM build at moment).
After that the attached pull request should work. I also need to add an
exclude, because there's one *new* jetty dependency, that is not part of
Lucene, but pulled in from Maven, so this needs fixing, too (otheriwse License
information is incorrect).
If nobody objects, I will proceed with that. Don't wonder if the attached pull
request gets "red" by removal of lines :-)
In a later stage I will check if artifact publishing to Apache Repos can be
updated to the new plugin maven-resolver-ant-tasks. But that's not so urgent,
we can live with parallel usage of both Ant plugins.
> 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
> Components: general/build
> Affects Versions: 8.x, 8.9
> Reporter: Uwe Schindler
> Priority: Major
> Fix For: 8.x
>
> Time Spent: 10m
> 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: [email protected]
For additional commands, e-mail: [email protected]
