[
https://issues.apache.org/jira/browse/CXF-5986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14127209#comment-14127209
]
Sergey Beryozkin commented on CXF-5986:
---------------------------------------
I prototyped some code for supporting includes/excludes, by copying some
relevant code from a WSDL plugin. This code creates a new WADLOption per every
discovered WADL file, and it gets the extra args from a 'wadlFileName-options'
files. The code also support a default WADL option, but I guess for it to work
the option inheritance/merge needs to be fixed first.
Additionally, I added the code which uses CXF ClassPathScanner. Suppose you
have all files in /src/main/resources/wadl, you'd just set a given wadlOption
wadl file to say "/wadl/" and the files will be found. The extra requirement
here is to add a spring-core to plugin dependencies only.
Can you please start experimenting with both includes/excludes and CXF
ClassPathScanner ? We can tune it eventually as needed...
Sergey
> wadl2java maven plugin: add support for filename wildcards
> ----------------------------------------------------------
>
> Key: CXF-5986
> URL: https://issues.apache.org/jira/browse/CXF-5986
> Project: CXF
> Issue Type: Improvement
> Components: Build system, Tooling
> Affects Versions: 3.0.1
> Environment: maven 3.1.1
> wadl2java
> Reporter: Matt Parker
> Priority: Minor
> Labels: maven
>
> I have a project with around 50 wadl files. Running wadl2java with the maven
> plugin, I currently must specify a separate execution for each individual
> file. I would like to be able to specify a wildcard like '**/*.wadl', or use
> includes/excludes, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
