On Sunday 19 September 2010 3:30:28 pm Andreas Veithen wrote: > The change in r993403 causes build failures in at least one downstream > project, namely Woden. Can we postpone the 1.4.7 release until this is > sorted out?
Fixed. Dan > > Andreas > > On Sun, Sep 19, 2010 at 17:27, Benson Margulies <bimargul...@gmail.com> wrote: > > The XmlSchema tree turned to be in a relatively clean state w/r/t a > > release. So, I've staged one. > > > > This email formally offers a candidate release 1.4.7 of Apache > > XmlSchema. The release artifacts are all sitting in the maven staging > > repository: > > > > https://repository.apache.org/content/repositories/orgapachews-042/ > > > > As usual, even the 'non-maven' files are in there. > > > > This vote will remain open for 72 hours. > > > > Here is my initial +1. > > > > Thanks, > > > > Benson Margulies > > > > > > Here are the release notes: > > > > Changes since 1.4.6: > > > > ** Bug > > * [WSCOMMONS-484] - Performance enhancement for build from DOM > > * (WSCOMMONS-361) breaks Xerces DOM > > Node's Java serializability > > * [WSCOMMONS-537] - Cached NodeNamespaceContext causes problems > > when a new namespace is added > > * [WSCOMMONS-539] - Infinite loop in XmlSchemaSerializer. > > setupNamespaces > > > > ** Improvement > > * [WSCOMMONS-520] - Add a setEntityResolver() to be used in > > XmlSchemaCollection.read > > * [WSCOMMONS-559] - Utils to ease use of XmlSchema in determining > > * instance attribute types -- Daniel Kulp dk...@apache.org http://dankulp.com/blog
