On Wed, 17 Jul 2002, Jon Scott Stevens wrote: > We are also talking about the next version of the Servlet API (5.0) which is > based on the work of JSR 154...not JSR 053. JSR 154 is specific to the > Servlet API and is not working on JSP. So, it no longer makes sense to have > the two together for the next revision of the Servlet API. > > 2 API's, 2 JSR's, 2 CVS repo's. >
As I said, xml.apache.org is packaging 3 APIs from 3 different and unrelated sources in a single repo and jar ( DOM, SAX, JAXP ), and that was discussed and aproved by both xalan and xerces communities. And we had allways distributed the 2 in a single jar and used a single repository. > We are at a -1 stalemate. Should we involve the Jakarta PMC now? As I said, I think this is a majority vote. I don't think naming or packaging or releases or code organisation can be decided by consensus, especially when there are multiple choices. And the current organisation got a pretty sensible majority. Besides, the current practice is to use a single repo/jar, there is no change proposed. You can't -1 a non-change, I think. I don't care too much about 2 repositories, but I do care about a single jar. And I don't like seeing the voting system abused. You can obviously raise the issue with the PMC. Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
