[
https://issues.apache.org/jira/browse/LENS-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14574134#comment-14574134
]
Raju Bairishetti edited comment on LENS-8 at 6/5/15 8:47 AM:
-------------------------------------------------------------
Can we fix log4j properties file in lens-server module as part of this jira?
Right now it is creating directory *lens-server* in the lens-server module
which won't be deleted with *mvn clean*
{noformat}
log4j.appender.TEST_LOG_FILE.File=lens-server/target/test.log
{noformat}
Can we store it in target/test.log or ${project.build.directory}/test.log?
was (Author: raju.bairishetti):
Can we fix log4j properties file in lens-server module as part of this jira?
Right now it is creating directory *lens-server* in the lens-server module
which won't be deleted with *mvn clean*
{noformat}
log4j.appender.TEST_LOG_FILE.File=lens-server/target/test.log
{noformat}
> Store test output in test specific file
> ---------------------------------------
>
> Key: LENS-8
> URL: https://issues.apache.org/jira/browse/LENS-8
> Project: Apache Lens
> Issue Type: Improvement
> Components: test
> Reporter: Srikanth Sundarrajan
> Assignee: Amareshwari Sriramadasu
> Fix For: 2.2
>
> Attachments: LENS-8.patch
>
>
> Current build is printing all output into console, mixing maven and test
> outputs together. This might make debugging test failures a bit involved. We
> can use surefire capability to store individual test outputs to respective
> files.
> I also happened to notice some test output printing on System.out directly,
> It would help if they can be routed through logging appender.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
