[
https://issues.apache.org/jira/browse/QUARKS-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252487#comment-15252487
]
ASF GitHub Bot commented on QUARKS-146:
---------------------------------------
GitHub user saurabhjinturkar opened a pull request:
https://github.com/apache/incubator-quarks/pull/96
QUARKS-146 [WIP]
Replaced e.printStackTrace() statements with logger errors.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/saurabhjinturkar/incubator-quarks
code_cleanup_QUARKS-146
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-quarks/pull/96.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 #96
----
commit 125c5a337525a22e1b54b219044494138cc9caf9
Author: Saurabh Jinturkar <[email protected]>
Date: 2016-04-21T19:12:06Z
replaced e.printStackTrace with logger
----
> cleanup e.printStackTrace() use
> -------------------------------
>
> Key: QUARKS-146
> URL: https://issues.apache.org/jira/browse/QUARKS-146
> Project: Quarks
> Issue Type: Bug
> Components: Runtime
> Reporter: Dale LaBossiere
> Priority: Minor
> Labels: newbie
>
> Ran across a use of e.printStackTrace() in runtime code where logging needs
> to be done instead. Looks like there are a few instances of this:
> AppServiceControl.java
> Executable.java
> Invocation.java
> IotfDeviceCommands.java
> There are also numerous uses in console/servlets. Do those need to be fixed
> too?
> $ cd incubator-quarks
> $ grep printStackTrace `find . -name *.java | grep -v test`
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
