[
https://jira.codehaus.org/browse/MJAXB-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283839#comment-283839
]
Robert Scholte commented on MJAXB-55:
-------------------------------------
* http://jaxb.java.net/nonav/2.2.1/docs/schemagen.html
* http://jaxb.java.net/nonav/2.2.1/docs/schemagenTask.html
As you could see, generation and renaming is done in two steps, the input and
outputdirectory are separated.
To stay close the ant-syntax we could add:
{code:xml}
<schemas>
<schema>
<namespace/>
<file/>
</schema>
</schemas>
{code}
we've already created a jaxb workingdirectory.
If there are schemas specified, use this workingdirectory, otherwise generate
does sources directly under {{target/generated-resources/jaxb}}
> Provide means to set the file name of generated XML schema
> ----------------------------------------------------------
>
> Key: MJAXB-55
> URL: https://jira.codehaus.org/browse/MJAXB-55
> Project: Maven 2.x JAXB 2.1 Plugin
> Issue Type: New Feature
> Affects Versions: 1.3.1
> Environment: All
> Reporter: Lennart Jörelid
> Assignee: Anders Hammar
> Attachments: fileRenamePatch.diff
>
>
> AbstractSchemagenMojo sneakily hard-codes the resulting filename for the
> generated schema file.
> This should really be configurable; provided a parameter to set the resulting
> file name, as well as an integration test.
> For reasons of somewhat misguided backwards compatibility, I set the default
> value of the parameter to its currently hardcoded value, "schema1.xsd".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
