[
http://jira.codehaus.org/browse/MNG-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MNG-3224:
------------------------------
Fix Version/s: 2.x
> Maven XML schemes are not usable in XML catalogs
> ------------------------------------------------
>
> Key: MNG-3224
> URL: http://jira.codehaus.org/browse/MNG-3224
> Project: Maven 2
> Issue Type: Improvement
> Reporter: Vojtech Habarta
> Fix For: 2.x
>
> Attachments: schemes.zip
>
>
> XML catalogs are usable especially for XML validation and in XML editors.
> They eliminate the need for schemaLocation attribute and online access to
> schema. They provide convenience and performance for XML processing. XML
> catalogs should map namespace to single schema file. This schema file can
> include other files but each namespace should be defined by single "primary"
> schema file.
> Unfortunately different maven schemes (maven-4.0.0.xsd, settings-1.0.0.xsd,
> etc.) define complex types with same name in the same namespace with
> different content.
> For Maven 2 I am suggesting quick solution which is to rename all repeating
> complex types to unique names and then either merge all schemes to one file
> or create simple "primary" schema file which would include all schema files.
> For Maven 3 I am suggesting to introduce different namespaces for different
> formats to allow separate versioning.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
