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