There seems to be an interaction between xs:redefine referring to a schema
which then does an xs:include that prevents Xerces from recognizing that an
attributeGroup defined in the xs:include'd schema has been extended to include
new attributes from a second namespace. I think this is a bug in
From: Mukul Gandhi> I would suggest, to open a bug report in Xerce's JIRA with
following
> qualifications [snip]
Thanks Mukul, I'll open a JIRA ticket as you suggest. I'll be sure to attach
all the files that are needed to reproduce the issue, as I don't think I'd be
able to implement a pa
From: David Costanzo
> Thanks Mukul, I'll open a JIRA ticket as you suggest.
As I went to open the ticket in JIRA, I found that Mukul Gandhi already fixed
it.
https://issues.apache.org/jira/browse/XERCESJ-1591
Thank you, Mukul!
The fix was made in the xml-schema-1.1-dev branch that
From: Michael Glavassevich
> Regarding a new Xerces release, I think we'd certainly like to see one
> happen, but it needs volunteers to help drive it.
I don't what skills/permissions a volunteer needs, but please let me know if
there's a way that someone who unfamiliar with the code base can h
From: Michael Glavassevich
> The release notes in JIRA (e.g. 2.11.0 notes [1]) and updates to the
> Xerces documentation [2] are something anyone could help us out with. We
> likely have a bunch of broken links that should be fixed up.
I started with the JIRA release notes [1] and it doesn't l
From: David Costanzo
> > I started with the JIRA release notes [1] and it doesn't look like I
> > have permissions to help with this. [snip]
From: Michael Glavassevich
> I just add you to the list of contributors in JIRA. Hopefully that also
> granted you permission to
