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

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

GitHub user vrozov opened a pull request:

    https://github.com/apache/drill/pull/1004

    DRILL-5876: Use openssl profile to include netty-tcnative dependency with 
the platform specific classifier

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/vrozov/drill DRILL-5876

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/drill/pull/1004.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1004
    
----
commit 575d09e8e4de6c9ff61ab53cb23e4aede29d2398
Author: Vlad Rozov <[email protected]>
Date:   2017-10-18T22:00:37Z

    DRILL-5876: Use openssl profile to include netty-tcnative dependency with 
the platform specific classifier

----


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

Reply via email to