[MNG-3224] Maven XML schemes are not usable in XML catalogs

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.10
• Assignee: Herve Boutemy
• Reporter: Vojtech Habarta
• Created: 28/Sep/07 04:28
• Updated: 06/Apr/15 00:47
• Resolved: 22/Dec/08 16:30

Description

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.

Issue Links

• is related to: MNG-3907 Profile XSD has wrong namespace
• is related to: MASSEMBLY-212 Assembly Descriptor Schemas (XSD) have wrong targetNamespace
• is related to: MNGSITE-140 Incorrect target namespace for http://maven.apache.org/xsd/plugin-metadata-1.0.0.xsd
• is related to: MNG-2636 Namespace settings-1.0.0.xsd correct?