[
https://jira.codehaus.org/browse/MJAXB-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283838#comment-283838
]
Lennart Jörelid edited comment on MJAXB-55 at 11/19/11 6:39 AM:
----------------------------------------------------------------
I agree that the best way of achieving this support would be to fix the problem
within the SchemaGenerator.
(The infamous "There is no way to control the name of the generated schema
files at this time." sentence seems to set the level here).
If such a thing is done one needs not only enable supplying proper file names
for generated schema,
but also provide namespace prefix control to avoid the "ns1:", "ns2:" syndrome.
However, we can rather quickly implement
both these things within the JAXB plugin; what are your time estimates for a
process to make these changes within the
SchemaGenerator?
I think I suggest doing both these things in parallel - we can easily switch
the transformation to arguments supplied to SchemaGenerator when we have such
opportunities.
The integration tests should still be useable in both scenarios.
was (Author: [email protected]):
I agree that the best way of achieving this support would be to fix the
problem within the SchemaGenerator.
(The infamous "There is no way to control the name of the generated schema
files at this time." sentence seems to set the level here).
If such a thing is done one needs not only enable supplying proper file names
for generated schema,
but also provide namespace prefix control to avoid the "ns1:", "ns2:" syndrome.
However, we can rather quickly implement
both these things within the JAXB plugin; what are your time estimates for a
process to make these changes within the
SchemaGenerator?
> 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
