Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-5217

disable transitive dependencies in maven config

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.7, 6.0
    • Component/s: None
    • Labels:
      None
    • Lucene Fields:
      New

      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.

        Attachments

        1. LUCENE-5217.patch
          132 kB
          Steven Rowe
        2. LUCENE-5217.patch
          152 kB
          Steven Rowe
        3. LUCENE-5217.patch
          153 kB
          Steven Rowe
        4. LUCENE-5217.patch
          153 kB
          Steven Rowe

        Issue Links

          Activity

            People

            • Assignee:
              sarowe Steven Rowe
              Reporter:
              rcmuir Robert Muir

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment