You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@parquet.apache.org by "Gabor Szadovszky (Jira)" <ji...@apache.org> on 2021/06/22 14:53:00 UTC

[jira] [Assigned] (PARQUET-2043) Fail build for used but not declared direct dependencies

     [ https://issues.apache.org/jira/browse/PARQUET-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gabor Szadovszky reassigned PARQUET-2043:
-----------------------------------------

    Assignee: Gabor Szadovszky

> Fail build for used but not declared direct dependencies
> --------------------------------------------------------
>
>                 Key: PARQUET-2043
>                 URL: https://issues.apache.org/jira/browse/PARQUET-2043
>             Project: Parquet
>          Issue Type: Improvement
>          Components: parquet-mr
>            Reporter: Gabor Szadovszky
>            Assignee: Gabor Szadovszky
>            Priority: Major
>
> 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|http://maven.apache.org/plugins/maven-dependency-plugin/analyze-only-mojo.html] can be used for this purpose.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)