[
https://issues.apache.org/jira/browse/QUARKS-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250660#comment-15250660
]
Dale LaBossiere commented on QUARKS-146:
----------------------------------------
Welcome to the community [[email protected]]!!!
Since you found yourself here you probably already found:
http://quarks.incubator.apache.org/docs/community
Subscribe to and use the "dev" mailing list for general questions, etc:
[email protected]
Then start here
https://github.com/apache/incubator-quarks/blob/master/DEVELOPMENT.md
The Quarks code uses slf4j for logging.
You can see an example of its use here:
https://github.com/apache/incubator-quarks/blob/0a95f3091afdc4f62abb9ffe82afa45d4a39781c/runtime/jobregistry/src/main/java/quarks/runtime/jobregistry/JobRegistry.java
> 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)
