[
https://issues.apache.org/jira/browse/CXF-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated CXF-851:
---------------------------
Attachment: xjc_usage_and_ts_tidy.gtully.patch
This patch adds support for -xjc-X such that it will report the usage string of
available XJC plugins. The list of plugins is build up dynamically from the
classpath by XJC.
The wsdl2java -xjc usage string is now more focused on the use case of loading
plugins, additional arguments should only be passed to -xjc by persons
knowledgeable of XJC and the way it is driven by CXF.
The distribution pom.xml now coorrectly adds the ts plugin to the modules.
The usage string of the ts and dv plugins look more similar from a formatting
perspective.
A simple test for the JAXBToStringBuilder is included.
> wsld2java -xjc usage is too minimal, there is no way to know what plugin
> options are available.
> -----------------------------------------------------------------------------------------------
>
> Key: CXF-851
> URL: https://issues.apache.org/jira/browse/CXF-851
> Project: CXF
> Issue Type: Improvement
> Components: Tooling
> Affects Versions: 2.0.1
> Reporter: Gary Tully
> Attachments: xjc_usage_and_ts_tidy.gtully.patch
>
>
> wsdl2java supports -xjc that can be used to pass args to XJC and have it load
> plugins. The primary focus of the option is to allow plugins to be loaded so
> it would be nice to know what plugins are available. Something like -xjc-X
> should show the available plugins.
> Also, the ts plugin should exist in the distribution modules not just in the
> manifest jar.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
