Matt Parker created CXF-5985:
--------------------------------
Summary: wadl2java maven plugin: executions don't use plugin-level
configuration
Key: CXF-5985
URL: https://issues.apache.org/jira/browse/CXF-5985
Project: CXF
Issue Type: Bug
Components: Build system, Tooling
Affects Versions: 3.0.1
Environment: maven 3.1.1
wadl2java
Reporter: Matt Parker
Priority: Minor
Specifying a configuration outside of an execution does not apply the expected
configuration to the execution.
According to
http://maven.apache.org/guides/mini/guide-configuring-plugins.html,
{quote}
Configurations inside the <executions> tag differ from those that are outside
<executions> in that they cannot be used from a direct command line invocation.
Instead they are only applied when the lifecycle phase they are bound to are
invoked. Alternatively, if you move a configuration section outside of the
executions section, it will apply globally to all invocations of the
plugin.{quote}
For example, I would like to be able to specify the catalog and extraargs
configuration at the plugin level, specify multiple executions, and have the
configuration apply to all executions. Similar to:
{code}
<plugin>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-wadl2java-plugin</artifactId>
<version>${cxf.wadltojava.version}</version>
<configuration>
<sourceRoot>${project.build.directory}/wadl2java</sourceRoot>
<catalog>catalog</catalog>
<extraargs>
<extraarg>-verbose</extraarg>
<extraarg>-inheritResourceParams</extraarg>
<extraarg>-noVoidForEmptyResponses</extraarg>
<extraarg>-compile</extraarg>
</extraargs>
</configuration>
<executions>
<execution>
<id>execution1</id>
...
<execution>
<id>execution2</id>
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
