Maven 2 & 3
  1. Maven 2 & 3
  2. MNG-2636

Namespace settings-1.0.0.xsd correct?

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 2.0.4
    • Fix Version/s: 2.0.10
    • Component/s: Settings
    • Labels:
      None
    • Environment:
      - Win XP
      - JDK 1.5
    • Complexity:
      Intermediate
    • Number of attachments :
      0

      Description

      Currently the namespace chosen in the settings XSD is the same as the
      one chosen in the POM XSD. This causes conflicts e.g. when using XML
      catalogs to resolve the XSD files (e.g. when using the WTP/XML Catalog
      support in Eclipse):

      POM XSD :

      http://maven.apache.org/maven-v4_0_0.xsd

      POM example:

      <project
      xmlns="http://maven.apache.org/POM/4.0.0"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
      ...
      </project>

      Settings XSD :

      http://maven.apache.org/xsd/settings-1.0.0.xsd

      Settings example :

      <settings
      xmlns="http://maven.apache.org/POM/4.0.0"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
      ...
      </settings>

      Having one namespace pointing to two different XSD files, depending on
      whether you're editing a POM or a settings file isn't a good idea.

      Question : can't the namespace of the settings XSD be changed or would
      this have too much of an impact on M2 (e.g. when M2 currently uses a
      namespace aware parser to parse the XML files)?

        Issue Links

          Activity

          Hide
          Vincent Siveton added a comment -

          I fixed it in r726420, updated the doc in r726433 and redeployed xsd (wait for the sync)

          Show
          Vincent Siveton added a comment - I fixed it in r726420, updated the doc in r726433 and redeployed xsd (wait for the sync)
          Hide
          Eugene Kuleshov added a comment -

          Strangely, I didn't had any problems to use wtp/xml catalogs in Eclipse with old files. But now I am concerned, how new schemas would work with existing settings.xml and profiles.xml?

          Show
          Eugene Kuleshov added a comment - Strangely, I didn't had any problems to use wtp/xml catalogs in Eclipse with old files. But now I am concerned, how new schemas would work with existing settings.xml and profiles.xml?
          Hide
          Vincent Siveton added a comment -

          Eugene, these files are the sames, just regenerated. I sent an email to users@ about new schema locations, so users need to update their files.

          Show
          Vincent Siveton added a comment - Eugene, these files are the sames, just regenerated. I sent an email to users@ about new schema locations, so users need to update their files.

            People

            • Assignee:
              Vincent Siveton
              Reporter:
              Davy Toch
            • Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: