[LUCENE-5217] disable transitive dependencies in maven config

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.7, 6.0
• Lucene Fields: New
• Assignee: Steven Rowe
• Reporter: Robert Muir
• Created: 15/Sep/13 23:12
• Updated: 28/Aug/22 13:53
• Resolved: 14/Nov/13 20:28

Description

Our ivy configuration does this: each dependency is specified and so we know what will happen. Unfortunately the maven setup is not configured the same way.

Instead the maven setup is configured to download the internet: and it excludes certain things specifically.

This is really hard to configure and maintain: we added a 'validate-maven-dependencies' that tries to fail on any extra jars, but all it really does is run a license check after maven "runs". It wouldnt find unnecessary dependencies being dragged in if something else in lucene was using them and thus they had a license file.

Since maven supports wildcard exclusions: MNG-3832, we can disable this transitive shit completely.

We should do this, so its configuration is the exact parallel of ivy.

Issue Links

• relates to: LUCENE-5420 'ant get-maven-poms' should support custom version formats