Uploaded image for project: 'Parquet'
  1. Parquet
  2. PARQUET-2043

Fail build for used but not declared direct dependencies

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

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: parquet-mr
    • Labels:
      None

      Description

      It is always a good practice to specify all the dependencies directly used (classes are imported from) by our modules. We have a couple of issues where classes are imported from transitive dependencies. It makes hard to validate the actual dependency tree and also may result in using wrong versions of classes (see PARQUET-2038 for example).

      It would be good to enforce to reference such dependencies directly in the module poms. The maven-dependency-plugin analyze-only goal can be used for this purpose.

        Attachments

          Activity

            People

            • Assignee:
              gszadovszky Gabor Szadovszky
              Reporter:
              gszadovszky Gabor Szadovszky

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment