[
https://issues.apache.org/jira/browse/BIGTOP-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14212828#comment-14212828
]
jay vyas edited comment on BIGTOP-1529 at 11/14/14 9:10 PM:
------------------------------------------------------------
Review of existing common/pom.xml.
- Maven plugin declaratioin 10 lines
- Generate of jars, another 10 lines
- Adding groovy exec to maven : 30 lines
- Adding env enforcer to maven : 23 lines
- failsafe plugin 40 lines w/ some sys properties for logging.
I think we can borrow from the failsafe log4j settings.
Probably we can also borrow the definitions of dependencies in the pom file.
ill give it a second look later on as well to see if other stuff can be unified.
was (Author: jayunit100):
Review of existing common/pom.xml.
- Maven plugin declaratioin 10 lines
- Generate of jars, another 10 lines
- Adding groovy exec to maven : 30 lines
- Adding env enforcer to maven : 23 lines
- failsafe plugin 40 lines w/ some sys properties for logging.
- I think we can borrow from the failsafe log4j settings.
- Probably we can also borrow the definitions of dependencies in the pom file.
ill give it a second look later on as well.
> Smoke tests should reuse the same log4j file
> --------------------------------------------
>
> Key: BIGTOP-1529
> URL: https://issues.apache.org/jira/browse/BIGTOP-1529
> Project: Bigtop
> Issue Type: Bug
> Reporter: David Capwell
>
> Currently the smoke tests will bundle and manage their own log4j details. It
> would be nice if a user can change this in one place and have it work for all
> tests. Would also be nice if a user can define different aspects such as
> level from CLI
> {code}
> ./gradlew clean test -Dsmoke.tests=pig -Dlog4j.logger.level=TRACE
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
