[
https://issues.apache.org/jira/browse/LUCENE-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726140#comment-16726140
]
Steve Rowe commented on LUCENE-8616:
------------------------------------
Related: Elasticsearch had wildcard exclusions for a while and then put back
their explicit exclusions, because 3rd-party tools like Ant didn't understand
wildcard exclusions, see https://github.com/elastic/elasticsearch/pull/24879
Ivy 2.5.0-rc1, released 8 months ago, includes wildcard exclusions support
(IVY-1531). There has been no discussion on the Ant dev mailing list about a
final 2.5.0 release, but I found an ivy-user@ post from an Ant dev (
https://lists.apache.org/thread.html/e911b9ea3b8c415de2927f3762ba0866465d95ee75aed6c6b336276a@%3Civy-user.ant.apache.org%3E
) that says:
{quote}
2.5.0-rc1 has a major issue that's being tracked as part of IVY-1580. I have
been working on it but haven't had enough time to get a right solution for it.
A fix for that would be necessary to release rc2 of Final of 2.5.0. I don't
have an exact time frame for the release, but I'll send a note on the dev list
once I have something.
{quote}
Unfortunately there has been no activity on IVY-1580 since then, and
Elasticsearch's latest POMs still have explicit exclusions.
Should we delay implementing wildcard exclusions until after Ivy 2.5.0 final
has been released?
> Maven build: Simplify the way transitive dependency resolution is disabled,
> and increase the minimum supported Maven from 2.2.1 to 3.2.1
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-8616
> URL: https://issues.apache.org/jira/browse/LUCENE-8616
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
> Reporter: Steve Rowe
> Assignee: Steve Rowe
> Priority: Major
>
> Right now the Maven build disables transitive dependency resolution for all
> dependencies by listing each dependency's dependencies in a nested
> {{<exclusions>}} section in the grandparent POM's {{<dependencyManagement>}}
> section.
> As of Maven 3.2.1, it's possible to use a wildcard syntax in nested
> {{<exclusions>}} sections to exclude all transitive deps: MNG-2315. This
> would make the grandparent POM much smaller and make the intent much clearer.
> We would have to increase our minimum supported Maven (currently 2.2.1), but
> that seems reasonable, given that Maven 2.x has been EOL'd:
> https://maven.apache.org/maven-2.x-eol.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
