On Wed, 17 Jul 2002, Jon Scott Stevens wrote:

> > Until the JSP 2.0 spec is changed, it make less sense for us to
> > have two separate repos.  (It just make more sense to put
> > javax.servlet.jsp.tagext.TagInfo with javax.servlet classes).
> 
> They can be in separate repo's with the same package name.
> 
> If Sun wants to distribute a combined .jar file from their website, then
> that is fine. 
> 
> But when the software lives on the Jakarta site, it should be in separate
> repo's.
> 
> As a committer on both Tomcat and Servlet API, co-founder of Jakarta, as
> well as a member of the ASF and JSR 053/154, here is my -1 based on the
> reasons I have already stated (and which 2 other people agreed with me on).

I believe this can't be a 'consensus' vote - at least the proposal
for the code organization was a 'majority' vote with multiple 
choices. 

This is how the repository was organized before, xml.apache.org
is doing the same for SAX and DOM and JAXP ( in xmlApis.jar ). 
Spliting it in 2 jars will create confusion - so I'm
-1 on spliting them up unless the JSR expert groups decide
so. 



Costin





--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to