[jira] [Commented] (AMBARI-18419) Allow setting EclipseLink weave log level in build process

2017-06-15 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-18419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16050389#comment-16050389
 ] 

Hudson commented on AMBARI-18419:
-

FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #1599 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/1599/])
AMBARI-18419. Allow setting EclipseLink weave log level in build process 
(adoroszlai: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=55891101d6c7c0662e82f8e9f6f20354a1337c71])
* (edit) ambari-server/pom.xml


> 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, 2.5.2
>
> 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.4.14#64029)

[jira] [Commented] (AMBARI-18419) Allow setting EclipseLink weave log level in build process

2017-06-15 Thread Doroszlai, Attila (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-18419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16050369#comment-16050369
 ] 

Doroszlai, Attila commented on AMBARI-18419:


Committed to 
[branch-2.5|http://git-wip-us.apache.org/repos/asf/ambari/commit/55891101d6].

> 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, 2.5.2
>
> 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.4.14#64029)

[jira] [Commented] (AMBARI-18419) Allow setting EclipseLink weave log level in build process

2016-09-21 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/AMBARI-18419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15509623#comment-15509623
 ] 

Hudson commented on AMBARI-18419:
-

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #5703 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5703/])
AMBARI-18419. Allow setting EclipseLink weave log level in build (stoader: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=20997630d5be2a0d684a779b0daecb33ec54a4d6])
* (edit) ambari-server/pom.xml


> 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)