[ https://issues.apache.org/jira/browse/AMBARI-18419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doroszlai, Attila updated AMBARI-18419: --------------------------------------- Resolution: Fixed Status: Resolved (was: Patch Available) Committed to trunk: commit 20997630d5be2a0d684a779b0daecb33ec54a4d6 > Allow setting EclipseLink weave log level in build process > ---------------------------------------------------------- > > Key: AMBARI-18419 > URL: https://issues.apache.org/jira/browse/AMBARI-18419 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.4.0 > Reporter: Doroszlai, Attila > Assignee: Doroszlai, Attila > Priority: Minor > Fix For: 3.0.0 > > Attachments: AMBARI-18419_20160921_v1.patch > > > Ambari Serveri's build process includes eclipselink-staticweave-maven-plugin, > with logLevel = ALL. This makes Maven output 17808 lines for EclipseLink > even if running with -q. > {noformat} > [INFO] --- eclipselink-staticweave-maven-plugin:1.0.4:weave (default) @ > ambari-server --- > [EL Finest]: jpa: 2016-09-19 > 16:52:30.507--ServerSession(1739278663)--Thread(Thread[main,5,main])--Begin > predeploying Persistence Unit ambari-server; session ambari-server; state > Initial; factoryCount 0 > [EL Finest]: properties: 2016-09-19 > 16:52:30.516--ServerSession(1739278663)--Thread(Thread[main,5,main])--property=eclipselink.weaving.changetracking; > default value=true > ... > {noformat} > The goal of this change is let developers to suppress EclipseLink log, while > keeping the current behavior as default. -- This message was sent by Atlassian JIRA (v6.3.4#6332)