[ 
https://issues.apache.org/jira/browse/GOBBLIN-1256?focusedWorklogId=482625&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-482625
 ]

ASF GitHub Bot logged work on GOBBLIN-1256:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 12/Sep/20 20:07
            Start Date: 12/Sep/20 20:07
    Worklog Time Spent: 10m 
      Work Description: ZihanLi58 commented on pull request #3099:
URL: 
https://github.com/apache/incubator-gobblin/pull/3099#issuecomment-691333583


   > It is also worth noting that tests like `LoggingPusherTest` will not work 
if running in IntellIJ without removing bridging jar from external library 
directories. So it will be better to document this kind of "Gotcha" as well.
   
   I haven't meet this error in intellij, maybe it randomly picks the right jar 
for me, will add this into the document


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 482625)
    Time Spent: 1h 20m  (was: 1h 10m)

> Make hive-exec as compileOnly for relevant modules
> --------------------------------------------------
>
>                 Key: GOBBLIN-1256
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1256
>             Project: Apache Gobblin
>          Issue Type: Task
>            Reporter: Zihan Li
>            Priority: Major
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> We want our project only expose slf4j and rely on user to determine which log 
> implementation to be used. And hive-exec has dependency on log4j, so we want 
> to make hive-exec as compileOnly for relevant modules to avoid bring in 
> log4j/log4j-extras dependency for downstream project



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to