[ 
https://issues.apache.org/jira/browse/CXF-8360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francisco Mateo updated CXF-8360:
---------------------------------
    Description: 
I'm developing a Gradle plugin that's based on the Maven cxf-codegen-plugin.

When I use wsdl2java to generate Java sources, the following logs get printed:
{code:java}
13:45:53.139 [main] DEBUG org.apache.velocity - Initializing Velocity, Calling 
init()...
13:45:53.140 [main] DEBUG org.apache.velocity - Starting Apache Velocity v2.2
13:45:53.143 [main] DEBUG org.apache.velocity - Default Properties resource: 
org/apache/velocity/runtime/defaults/velocity.properties
13:45:53.148 [main] DEBUG org.apache.velocity - ResourceLoader instantiated: 
org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader
13:45:53.149 [main] DEBUG org.apache.velocity - initialized (class 
org.apache.velocity.runtime.resource.ResourceCacheImpl) with class 
java.util.Collections$SynchronizedMap cache map.
--- snip
{code}
Logs from Apache CXF are easily silenced by specifying 
{{-Dorg.apache.cxf.Logger=null}}, but the same can't be said for Apache 
Velocity.

The fix for CXF-7405 unintentionally enabled debug logs for velocity by 
commenting out the if condition for log.

It would be nice if we could have some sort of control of velocity logging with 
some sort of JVM argument.

Or partially revert [https://github.com/apache/cxf/pull/282] so the commented 
out log condition is restored since it looks like logs were originally disabled 
anyways.

  was:
I'm developing a Gradle plugin that's based on the Maven cxf-codegen-plugin.

When I use wsdl2java to generate Java sources, the following logs get printed:
{code:java}
13:45:53.139 [main] DEBUG org.apache.velocity - Initializing Velocity, Calling 
init()...
13:45:53.140 [main] DEBUG org.apache.velocity - Starting Apache Velocity v2.2
13:45:53.143 [main] DEBUG org.apache.velocity - Default Properties resource: 
org/apache/velocity/runtime/defaults/velocity.properties
13:45:53.148 [main] DEBUG org.apache.velocity - ResourceLoader instantiated: 
org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader
13:45:53.149 [main] DEBUG org.apache.velocity - initialized (class 
org.apache.velocity.runtime.resource.ResourceCacheImpl) with class 
java.util.Collections$SynchronizedMap cache map.
--- snip
{code}
Logs from Apache CXF are easily silenced by specifying 
{{-Dorg.apache.cxf.Logger=null}}, but the same can't be said for Apache 
Velocity.

 

The fix for CXF-7405 unintentionally enabled debug logs for velocity by 
commenting out the if condition for log.

It would be nice if we could have some sort of control of velocity logging with 
some sort of JVM argument.

Or partially revert [https://github.com/apache/cxf/pull/282] so the commented 
out log condition is restored since it looks like logs were originally disabled 
anyways.


> Configurable property for Apache Velocity logs
> ----------------------------------------------
>
>                 Key: CXF-8360
>                 URL: https://issues.apache.org/jira/browse/CXF-8360
>             Project: CXF
>          Issue Type: Improvement
>            Reporter: Francisco Mateo
>            Priority: Minor
>
> I'm developing a Gradle plugin that's based on the Maven cxf-codegen-plugin.
> When I use wsdl2java to generate Java sources, the following logs get printed:
> {code:java}
> 13:45:53.139 [main] DEBUG org.apache.velocity - Initializing Velocity, 
> Calling init()...
> 13:45:53.140 [main] DEBUG org.apache.velocity - Starting Apache Velocity v2.2
> 13:45:53.143 [main] DEBUG org.apache.velocity - Default Properties resource: 
> org/apache/velocity/runtime/defaults/velocity.properties
> 13:45:53.148 [main] DEBUG org.apache.velocity - ResourceLoader instantiated: 
> org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader
> 13:45:53.149 [main] DEBUG org.apache.velocity - initialized (class 
> org.apache.velocity.runtime.resource.ResourceCacheImpl) with class 
> java.util.Collections$SynchronizedMap cache map.
> --- snip
> {code}
> Logs from Apache CXF are easily silenced by specifying 
> {{-Dorg.apache.cxf.Logger=null}}, but the same can't be said for Apache 
> Velocity.
> The fix for CXF-7405 unintentionally enabled debug logs for velocity by 
> commenting out the if condition for log.
> It would be nice if we could have some sort of control of velocity logging 
> with some sort of JVM argument.
> Or partially revert [https://github.com/apache/cxf/pull/282] so the commented 
> out log condition is restored since it looks like logs were originally 
> disabled anyways.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to