[
https://issues.apache.org/jira/browse/CXF-8998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18097908#comment-18097908
]
Karl Heinz Marbaise commented on CXF-8998:
------------------------------------------
It took some time to have another occurance of the issue.
I've found the problem with the plugin (current version the same behaviour
4.2.2).
In the
https://github.com/apache/cxf/blob/main/maven-plugins/codegen-plugin/src/main/java/org/apache/cxf/maven_plugin/wsdl2java/WSDL2JavaMojo.java#L55
the Mojo Definition is as follows:
{code:java}
@Mojo(name = "wsdl2java", defaultPhase = LifecyclePhase.GENERATE_SOURCES,
threadSafe = true,
requiresDependencyResolution = ResolutionScope.TEST)
{code}
The issue is that the {{requiredDependencyResolution}} is set to
{{ResolutionScope.Test}} which means during the code generation it uses
TEST-Scoped dependencies (classpath) which can cause such an issue or others
like producing WARNINGS related to SLF4J if {{slf4j-simple}} or {{slf4j-nop}}
dependencies are used in {{test}} scope.
>From my point of view the {{requiredDependencyResolution}} should be defined
>as {{ResolutonScope.COMPILE}} which would also related to the definition of
>the default life cycle phase.
I will try to create a full reproducer...
> cxf-codegen-plugin - debug output velocity
> ------------------------------------------
>
> Key: CXF-8998
> URL: https://issues.apache.org/jira/browse/CXF-8998
> Project: CXF
> Issue Type: Improvement
> Components: Configuration
> Affects Versions: 4.0.4
> Reporter: Karl Heinz Marbaise
> Priority: Minor
>
> Currently we are using {{cxf-codegen-plugin}}, which produces allways
> debugging output of velocity, on the console
> {code}
> 15:59:45 [INFO]
> 15:59:45 [INFO] --- cxf-codegen:4.0.4:wsdl2java (default) @ wsdls ---
> 15:59:45 [INFO] Running code generation in fork mode...
> 15:59:45 [INFO] bin/java
> 15:59:45 [INFO] Building jar: /tmp/cxf-tmp-77777/cxf-codegenxxxx.jar
> 15:59:45 [WARNING] Picked up JAVA_TOOL_OPTIONS: .....
> 15:59:46 [INFO] 15:59:46.356 [main] DEBUG org.apache.velocity --
> Initializing Velocity, Calling init()...
> 15:59:46 [INFO] 15:59:46.360 [main] DEBUG org.apache.velocity -- Starting
> Apache Velocity v2.3
> 15:59:46 [INFO] 15:59:46.362 [main] DEBUG org.apache.velocity -- Default
> Properties resource: org/apache/velocity/runtime/defaults/velocity.properties
> 15:59:53 [INFO]
> {code}
> Is there an easy way to suppress the debug output for the execution of the
> plugin?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
