One important concern here is the restrictions this may place on releases of non-Commons ws projects.
Jakarta Struts, for example, has had its 1.1 final release held up literally for months because they use packages in jakarta-commons that are not at an appropriate release level. If one of the ws commons packages is incorporated into Axis, does that mean subsequent Axis releases will be tied to releases of the commons packages? What is the release criteria when an Axis commiter incorporates functionality from a nightly build of one of the commons packages? Does the Axis release then have to wait for the commons package to hit a release as well? Can Axis have a release if it incorporates code from a commons nightly build? --------------------------------------------------------------------------- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender and erase this e-mail message immediately. ---------------------------------------------------------------------------
