[
https://issues.apache.org/jira/browse/CXFXJC-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610046#comment-14610046
]
ASF GitHub Bot commented on CXFXJC-11:
--------------------------------------
GitHub user mbert opened a pull request:
https://github.com/apache/cxf-xjc-utils/pull/2
Convenience option for configuring the code generation from XSD files:
Instead of having to explicitly list every single file using the '<xsd>'
element, now the new '<xsdDir>' element can be used instead for
specifying a directory. From this directory all '*.xsd' files will be
used for code generation.
See also the ticket I opened in JIRA:
https://issues.apache.org/jira/browse/CXFXJC-11
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mbert/cxf-xjc-utils master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cxf-xjc-utils/pull/2.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2
----
commit fb0162e35f313bebc0d92ab089f0905ade7f2b79
Author: Martin Dietze <[email protected]>
Date: 2015-06-17T13:12:38Z
Convenience option for configuring the code generation from XSD files:
Instead of having to explicitly list every single file using the '<xsd>'
element, now the new '<xsdDir>' element can be used instead for
specifying a directory. From this directory all '*.xsd' files will be
used for code generation.
----
> Simplify code generation configuration in pom.xml (patch included)
> ------------------------------------------------------------------
>
> Key: CXFXJC-11
> URL: https://issues.apache.org/jira/browse/CXFXJC-11
> Project: CXF XJC Utils
> Issue Type: Improvement
> Components: Maven Plugin
> Reporter: Martin Dietze
> Priority: Minor
> Labels: maven, patch
> Attachments:
> 0001-Convenience-option-for-configuring-the-code-generati.patch
>
>
> Currently the configuration for the Java code generation from XSD files is
> unnecessarily verbose and bloats the pom.xml file in large projects.
> In all projects I have used this in so far, simply specifying the XSD source
> directory from which all XSD files would be taken would have been totally
> sufficient.
> I therefore propose to extend the the 'xsdOption' by another element:
> 'xsdDir'. If 'xsdDir' is configured and points to a directory, all XSD files
> found in it will be processed. If omitted, the existing 'xsd' element will be
> mandatory as it had been without this patch.
> I have created a patch implementing this functionality and added it to this
> ticket.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
