maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Herve Boutemy (JIRA)" <>
Subject [jira] Closed: (MNG-3224) Maven XML schemes are not usable in XML catalogs
Date Mon, 22 Dec 2008 22:31:19 GMT


Herve Boutemy closed MNG-3224.

         Assignee: Herve Boutemy
       Resolution: Fixed
    Fix Version/s:     (was: 3.x)

toolchain fixed in r728800, 728801, 728802, 728803 for Maven 3.0.x, 2.0.10-RC, 2.0.x and 2.1.x
plugin-metadata fixed in r728813 and redeployed to

> Maven XML schemes are not usable in XML catalogs
> ------------------------------------------------
>                 Key: MNG-3224
>                 URL:
>             Project: Maven 2
>          Issue Type: Improvement
>            Reporter: Vojtech Habarta
>            Assignee: Herve Boutemy
>             Fix For: 2.0.10
>         Attachments:
> 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:
For more information on JIRA, see:


View raw message