You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Aditya Kishore (JIRA)" <ji...@apache.org> on 2014/08/18 09:28:19 UTC
[jira] [Assigned] (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:all-tabpanel ]
Aditya Kishore reassigned DRILL-632:
------------------------------------
Assignee: Aditya Kishore
> 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
> Components: Client - JDBC
> Affects Versions: 0.4.0
> Reporter: Jacques Nadeau
> Assignee: Aditya Kishore
> Priority: Minor
> Fix For: 0.5.0
>
> Attachments: DRILL-632-JDBC-single-jar-build-failing-too-many-cla.patch
>
>
> 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)