[
https://issues.apache.org/jira/browse/PIRK-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400816#comment-15400816
]
ASF GitHub Bot commented on PIRK-28:
------------------------------------
Github user ellisonanne commented on the issue:
https://github.com/apache/incubator-pirk/pull/33
If you run the QuerierDriver (or ResponderDriver) locally you can test it
out. For example, if you run
`java -cp target/pirk-0.0.1-SNAPSHOT-exe.jar
org.apache.pirk.querier.wideskies.QuerierDriver`
it will use the properties loaded from the querier.properties file packaged
with the jar and should bark the error messages from QuerierProps. Currently,
it does not; you will just get the help message that prints out via
QuerierDriverCLI line 71. If you change all logger.info/logger.error messages
in QuerierProps to System.out.println you will see the output that you are
supposed to see via the logging mechanisms.
> 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)
