You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Adrian Sandor (JIRA)" <ji...@apache.org> on 2008/02/27 18:19:51 UTC
[jira] Created: (IVY-750) XML schema ambiguity
XML schema ambiguity
--------------------
Key: IVY-750
URL: https://issues.apache.org/jira/browse/IVY-750
Project: Ivy
Issue Type: Bug
Affects Versions: 2.0.0-beta-2
Reporter: Adrian Sandor
While running ivy built from svn, trying to resolve an ivy file, I got this message:
[Error] :43:30: cos-nonambig: "":license and WC[##any] (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
It doesn't seem to affect the functionality.
Xavier commented: "this probably due to the xs:any we have added in the info tag definition in our xsd. Adding a namespace="##other" to the xs:any to tell the parser that any element *from other namespace* is allowed should fix the problem"
Also see IVY-156
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVY-750) XML schema ambiguity
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xavier Hanin resolved IVY-750.
------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.0)
2.0-RC1
I've worked to fix this issue, but didn't reproduce the same problem. This may be due to the XML parser used. I've done the change I suggested (allowing extra info in other namespace only), which revealed some problems with the current parsing and ordering of extra info in files under test. Things should be cleaner and more robust now.
Adrian, if you can test the trunk version on your own and see if this problem is fixed for you, then we could close the issue.
> XML schema ambiguity
> --------------------
>
> Key: IVY-750
> URL: https://issues.apache.org/jira/browse/IVY-750
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-beta-2
> Reporter: Adrian Sandor
> Assignee: Xavier Hanin
> Fix For: 2.0-RC1
>
>
> While running ivy built from svn, trying to resolve an ivy file, I got this message:
> [Error] :43:30: cos-nonambig: "":license and WC[##any] (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
> It doesn't seem to affect the functionality.
> Xavier commented: "this probably due to the xs:any we have added in the info tag definition in our xsd. Adding a namespace="##other" to the xs:any to tell the parser that any element *from other namespace* is allowed should fix the problem"
> Also see IVY-156
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (IVY-750) XML schema ambiguity
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xavier Hanin reassigned IVY-750:
--------------------------------
Assignee: Xavier Hanin
> XML schema ambiguity
> --------------------
>
> Key: IVY-750
> URL: https://issues.apache.org/jira/browse/IVY-750
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-beta-2
> Reporter: Adrian Sandor
> Assignee: Xavier Hanin
> Fix For: 2.0
>
>
> While running ivy built from svn, trying to resolve an ivy file, I got this message:
> [Error] :43:30: cos-nonambig: "":license and WC[##any] (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
> It doesn't seem to affect the functionality.
> Xavier commented: "this probably due to the xs:any we have added in the info tag definition in our xsd. Adding a namespace="##other" to the xs:any to tell the parser that any element *from other namespace* is allowed should fix the problem"
> Also see IVY-156
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVY-750) XML schema ambiguity
Posted by "Xavier Hanin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xavier Hanin updated IVY-750:
-----------------------------
Fix Version/s: 2.0
> XML schema ambiguity
> --------------------
>
> Key: IVY-750
> URL: https://issues.apache.org/jira/browse/IVY-750
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-beta-2
> Reporter: Adrian Sandor
> Fix For: 2.0
>
>
> While running ivy built from svn, trying to resolve an ivy file, I got this message:
> [Error] :43:30: cos-nonambig: "":license and WC[##any] (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
> It doesn't seem to affect the functionality.
> Xavier commented: "this probably due to the xs:any we have added in the info tag definition in our xsd. Adding a namespace="##other" to the xs:any to tell the parser that any element *from other namespace* is allowed should fix the problem"
> Also see IVY-156
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-750) XML schema ambiguity
Posted by "Steve Loughran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620234#action_12620234 ]
Steve Loughran commented on IVY-750:
------------------------------------
I should warn that ##other is interpreted differently by different parsers. As long as everyone only uses xerces, all is well, but some (certainly the .NET ones) have different rules about ##local being in/out the ##other namespace.
> XML schema ambiguity
> --------------------
>
> Key: IVY-750
> URL: https://issues.apache.org/jira/browse/IVY-750
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-beta-2
> Reporter: Adrian Sandor
> Assignee: Xavier Hanin
> Fix For: 2.0-RC1
>
>
> While running ivy built from svn, trying to resolve an ivy file, I got this message:
> [Error] :43:30: cos-nonambig: "":license and WC[##any] (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
> It doesn't seem to affect the functionality.
> Xavier commented: "this probably due to the xs:any we have added in the info tag definition in our xsd. Adding a namespace="##other" to the xs:any to tell the parser that any element *from other namespace* is allowed should fix the problem"
> Also see IVY-156
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-750) XML schema ambiguity
Posted by "Adrian Sandor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572989#action_12572989 ]
Adrian Sandor commented on IVY-750:
-----------------------------------
Looks like jira interpreted ##any between square brackets as a link
> XML schema ambiguity
> --------------------
>
> Key: IVY-750
> URL: https://issues.apache.org/jira/browse/IVY-750
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-beta-2
> Reporter: Adrian Sandor
>
> While running ivy built from svn, trying to resolve an ivy file, I got this message:
> [Error] :43:30: cos-nonambig: "":license and WC[##any] (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
> It doesn't seem to affect the functionality.
> Xavier commented: "this probably due to the xs:any we have added in the info tag definition in our xsd. Adding a namespace="##other" to the xs:any to tell the parser that any element *from other namespace* is allowed should fix the problem"
> Also see IVY-156
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (IVY-750) XML schema ambiguity
Posted by "rednix (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620223#action_12620223 ]
rednix commented on IVY-750:
----------------------------
Just checked this issue with the current trunk version - it's fixed and therefore working.
> XML schema ambiguity
> --------------------
>
> Key: IVY-750
> URL: https://issues.apache.org/jira/browse/IVY-750
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0.0-beta-2
> Reporter: Adrian Sandor
> Assignee: Xavier Hanin
> Fix For: 2.0-RC1
>
>
> While running ivy built from svn, trying to resolve an ivy file, I got this message:
> [Error] :43:30: cos-nonambig: "":license and WC[##any] (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
> It doesn't seem to affect the functionality.
> Xavier commented: "this probably due to the xs:any we have added in the info tag definition in our xsd. Adding a namespace="##other" to the xs:any to tell the parser that any element *from other namespace* is allowed should fix the problem"
> Also see IVY-156
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.