Thanks Chris, I'd say let's go with the current jsr173_api.jar for now and when we update the Maven repository (after release), we'll add the dependency to stax-api there. This way, Maven people are happy, users downloading the release are happy (because they don't need to change their classpath) and people who want the release and stax-api can also get what they want obviously.
On the other hand, about XMLBEANS-330 and XMLBEANS-324 (the QName class conflict), after putting in some thought, I would actually like to clean that up before the release and move the offending classes in a different jar. I have the change ready to check in, but after that we would need to create a new RC... Radu On Tue, 2007-05-08 at 10:15 +0100, Chris wrote: > My module tests still work fine with this version. > Have you looked at bug 308 (use stax-api-1.0.1 instead of jsr173-1.0) > since January? Seems like an easy change if it's all ASL... > https://issues.apache.org/jira/browse/XMLBEANS-308 > > +1 from me > Chris > Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
