[AMBARI-18419] Allow setting EclipseLink weave log level in build process

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.4.0
• Fix Version/s: 3.0.0, 2.5.2
• Component/s: ambari-server
• Assignee: Attila Doroszlai
• Reporter: Attila Doroszlai
• Created: 19/Sep/16 14:59
• Updated: 15/Jun/17 12:09
• Resolved: 21/Sep/16 09:27

Description

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.

[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
...

The goal of this change is let developers to suppress EclipseLink log, while keeping the current behavior as default.

Issue Links

• links to: Review request