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

Steve Rowe edited comment on LUCENE-8616 at 12/20/18 8:25 PM:
--------------------------------------------------------------

About the size of the grandparent POM generated with the patch: it's 75% 
smaller: 101KB vs. 386KB; and 3K lines vs. 11K lines.


was (Author: steve_rowe):
About the size of the grandparent POM generated with the patched Maven build: 
it's 75% smaller: 101KB vs. 386KB; and 3K lines vs. 11K lines.

> 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
>         Attachments: LUCENE-8616.patch
>
>
> 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]

Reply via email to