As long as 1.0.1 hasn't been announced I'd prefer to roll this fix into 1.0.1 rather than have a release with a known glaring bug.
Lawrence Mandel Dan Diephouse <[EMAIL PROTECTED]> 04/09/2006 10:17 PM Please respond to [email protected] To [email protected] cc Subject Re: [vote] Release XmlSchema 1.0.2 to fix critical bug Well, I already pushed out jars/sources but I supposed can overwrite them. Thoughts? Any care if I just wrap this into 1.0.1? - Dan Srinath Perera wrote: >Dan why didn't we fix the bug and call it 1.0.1. Since you have not >announce 1.0.1, why we should call it 1.0.2? >Srinath > >On 4/9/06, Dan Diephouse <[EMAIL PROTECTED]> wrote: > > >>Hi everyone, >> >>I know I haven't announced the 1.0.1 release, but I would like to skip >>the announcement and proceed with a 1.0.2 release. I found a critical >>bug where with WSDLs such as the salesforce.com one, XmlSchema wasn't >>reading in schemas into the correct target namespace. The problem arises >>because it would actually recurse up to the <wsdl> element, read in the >>target namespace and set the current XmlSchema for that target namespace >>(in addition to its own target namespace). Suffice to say, this would >>cause XmlSchema to not function correctly with a lot of WSDLs (like >>salesforce.com). I would like to see this remedied in a release ASAP. >> >>So throw in your -1, 0, or +1! >> >>- Dan >> >>-- >>Dan Diephouse >>(616) 971-2053 >>Envoi Solutions LLC >>http://netzooid.com >> >> >> >> > > >-- >============================ >Srinath Perera: > http://www.cs.indiana.edu/~hperera/ > http://www.bloglines.com/blog/hemapani > > -- Dan Diephouse (616) 971-2053 Envoi Solutions LLC http://netzooid.com
