[jira] Commented: (MNG-2636) Namespace settings-1.0.0.xsd correct?

2008-12-15 Thread Eugene Kuleshov (JIRA)

[ 
http://jira.codehaus.org/browse/MNG-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158043#action_158043
 ] 

Eugene Kuleshov commented on MNG-2636:
--

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?

 Namespace settings-1.0.0.xsd correct?
 -

 Key: MNG-2636
 URL: http://jira.codehaus.org/browse/MNG-2636
 Project: Maven 2
  Issue Type: Improvement
  Components: Settings
Affects Versions: 2.0.4
 Environment: - Win XP
 - JDK 1.5
Reporter: Davy Toch
Assignee: Vincent Siveton
Priority: Minor
 Fix For: 2.0.10


 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)?

-- 
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




[jira] Commented: (MNG-2636) Namespace settings-1.0.0.xsd correct?

2008-12-15 Thread Vincent Siveton (JIRA)

[ 
http://jira.codehaus.org/browse/MNG-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158046#action_158046
 ] 

Vincent Siveton commented on MNG-2636:
--

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.

 Namespace settings-1.0.0.xsd correct?
 -

 Key: MNG-2636
 URL: http://jira.codehaus.org/browse/MNG-2636
 Project: Maven 2
  Issue Type: Improvement
  Components: Settings
Affects Versions: 2.0.4
 Environment: - Win XP
 - JDK 1.5
Reporter: Davy Toch
Assignee: Vincent Siveton
Priority: Minor
 Fix For: 2.0.10


 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)?

-- 
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