[
https://issues.apache.org/jira/browse/PIRK-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400255#comment-15400255
]
ASF GitHub Bot commented on PIRK-28:
------------------------------------
GitHub user smarthi opened a pull request:
https://github.com/apache/incubator-pirk/pull/33
[PIRK-28] [WIP]: Logger Statements Not Working in/from Drivers
I do see that the log4j2.properties is being packaged into target/classes
folder, and the main method should automatically pick it up from there.
There was an unnecessary dependency on log4j 1.2 in POM which has now been
removed and could have been shadowing the log4j2 jar.
Could someone please test this patch and confirm if its working? I'll check
on this later tonight.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/smarthi/incubator-pirk PIRK-28
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-pirk/pull/33.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 #33
----
commit 3fde0ae94144b6a147455b352420a9693ddbebfc
Author: smarthi <[email protected]>
Date: 2016-07-29T23:44:03Z
PIRK-28 : Logger Statements Not Working in/from Drivers
----
> Logger Statements Not Working in/from Drivers
> ---------------------------------------------
>
> Key: PIRK-28
> URL: https://issues.apache.org/jira/browse/PIRK-28
> Project: PIRK
> Issue Type: Bug
> Reporter: Ellison Anne Williams
> Assignee: Suneel Marthi
>
> Noticed today that logging is not functioning within the QuerierDriver and
> ResponderDriver (and the corresponding CLI classes). It does, however, appear
> to be working correctly when running through the unit tests (i.e. not calling
> a main() first).
> More investigation to get to the root cause is needed...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
