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

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

ASF GitHub Bot commented on PARQUET-2043:
-----------------------------------------

gszadovszky merged pull request #916:
URL: https://github.com/apache/parquet-mr/pull/916


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@parquet.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> 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)