[ https://issues.apache.org/jira/browse/DRILL-7179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16818896#comment-16818896 ]
Georgi Perpeliev commented on DRILL-7179: ----------------------------------------- [~lhfei] I managed to compile it successfully today after reverting maven's settings.xml to default (my company uses a custom one). Before it was compiling without errors or warnings, but without those jars. So it seems it was a transient maven issue and this one can be closed. Thanks for your help. I had checked out the tag drill-1.15.0 and compiled against it, it seems to point to the same commit as the branch. > Compiling drill from source doesn't include all the jars in the > distribution/target dir > --------------------------------------------------------------------------------------- > > Key: DRILL-7179 > URL: https://issues.apache.org/jira/browse/DRILL-7179 > Project: Apache Drill > Issue Type: Bug > Affects Versions: 1.15.0 > Environment: Building on Windows 10 > Reporter: Georgi Perpeliev > Assignee: Hefei Li > Priority: Minor > Attachments: checkou.png, cmpiled.png, verify_tarball_file.png > > > Following the instructions on > [https://drill.apache.org/docs/compiling-drill-from-source/] , we end up with > incomplete tarball including only drill-shaded-guava-23.0.jar in the jars > subdirectory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)