Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Fri, 13 Oct 2017 20:34:01 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.13109318.1507915562000.7642.1507926841844@Atlassian.JIRA>
In-Reply-To: <JIRA.13109318.1507915562000@Atlassian.JIRA>
References: <JIRA.13109318.1507915562000@Atlassian.JIRA> <JIRA.13109318.1507915562039@jira-lw-us.apache.org>
Subject: [jira] [Commented] (DRILL-5876) Remove netty-tcnative inclusion in
 java-exec/pom.xml
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 13 Oct 2017 20:34:08 -0000


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

ASF GitHub Bot commented on DRILL-5876:
---------------------------------------

Github user parthchandra commented on a diff in the pull request:

    https://github.com/apache/drill/pull/991#discussion_r144651132
  
    --- Diff: exec/java-exec/pom.xml ---
    @@ -701,18 +707,21 @@
           <!--
           Include the os-maven-plugin to get os.detected.classifier
           -->
    -      <extension>
    -        <groupId>kr.motd.maven</groupId>
    -        <artifactId>os-maven-plugin</artifactId>
    -        <version>1.5.0.Final</version>
    -      </extension>
    -    </extensions>
    +      <!-- Uncomment the following to get a debug build that allows openssl support -->
    --- End diff --
    
    How would that work in conjunction with the main pom's profiles? I would want to have both the (apache | mapr | cdh | hdp)  profile and the openssl profile enabled.


> Remove netty-tcnative inclusion in java-exec/pom.xml
> ----------------------------------------------------
>
>                 Key: DRILL-5876
>                 URL: https://issues.apache.org/jira/browse/DRILL-5876
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Parth Chandra
>
> The inclusion of netty-tcnative is causing all kinds of problems. The os specific classifier  required is determined by a maven extension which in turn requires an additional eclipse plugin. The eclipse plugin has a problem that may corrupt the current workspace.
> It is safe to not include the dependency since it is required only at runtime. The only case in which this is required is when a developer has to debug SSL/OpenSSL issues in the Java client or the server when launching from within an IDE. In this case, the dependency can be enabled by uncommenting the relevant lines in the pom file.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)