You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by "Patrick Wong (JIRA)" <ji...@apache.org> on 2014/05/05 20:19:16 UTC

[jira] [Commented] (DRILL-632) JDBC single jar build failing, too many classes

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

Patrick Wong commented on DRILL-632:
------------------------------------

Getting it to build was pretty simple: https://github.com/pwong-mapr/incubator-drill/commit/f8f6ca10c238671868eca95fccf4e195cd5d9c0f

For the spreadsheet - do you have a non-company account to host it? Although I could host the spreadsheet, it would only be visible to people at MapR, which is not appropriate for an Apache project.

> JDBC single jar build failing, too many classes
> -----------------------------------------------
>
>                 Key: DRILL-632
>                 URL: https://issues.apache.org/jira/browse/DRILL-632
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Jacques Nadeau
>            Assignee: Patrick Wong
>
> This jdbc-all module is now merged in master as exec/jdbc-all.  However, it is not included in the main build because it seems to fail to build in my tests.  Can you please reverify completion.  Secondly, we need to substantially reduce the class count.  It looks like we're currently sourcing more than 7k classes and I don't think we need near that many.  Can you create a google spreadsheet of all the classes included and add to this jira so we can discuss what might be able to be excluded.



--
This message was sent by Atlassian JIRA
(v6.2#6252)