[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> 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 an
On Wed, 17 Jul 2002, Jon Scott Stevens wrote:
> on 7/17/02 3:50 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>
> > 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
On Wed, 17 Jul 2002, Jon Scott Stevens wrote:
> Date: Wed, 17 Jul 2002 15:30:05 -0700
> From: Jon Scott Stevens <[EMAIL PROTECTED]>
> Reply-To: Tomcat Developers List <[EMAIL PROTECTED]>
> To: tomcat-dev <[EMAIL PROTECTED]>
> Subject: Re: Missed vote
>
>
on 7/17/02 3:50 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> 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.
Those 3 api's are co
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 fo
on 7/17/02 2:47 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> so I'm
> -1 on spliting them up unless the JSR expert groups decide
> so.
As Craig mentioned on the JSR 154 list, this isn't a JSR decision and I
wasn't talking about splitting the jar's up...Sun can distribute whatever
they w
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 packa
on 7/17/02 1:30 PM, "Kin-Man Chung" <[EMAIL PROTECTED]> wrote:
> I am sympathetic to Jon's view on separating servlet and JSP API
> and repositories.
>
> One result of the separation would make it likely that package names
> for JSP 2.0 API may change. JSP2.0 is now in public review, so it may
l 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).
> Date: Wed, 17 Jul 2002 20:28:43 +0200
> From: Paulo Gaspar <[EMAIL PROTECTED]>
> Subject: RE: Miss
For what is worth, I think Jon is 100% right on this one.
And he was cristal clear about the reasons too.
Regards,
Paulo
> -Original Message-
> From: Jon Scott Stevens [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 17, 2002 12:43 AM
> To: tomcat-dev
> Subject:
on 7/16/02 1:14 PM, "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote:
> What's so painful about a ten-line build.xml target that creates a
> separate JAR file with just the javax.servlet and javax.servlet.http API
> classes, if that's what you need?
>
> Sharing a CVS repository has little or noth
>> To: tomcat-dev <[EMAIL PROTECTED]>
>> Subject: Missed vote
>>
>> Arg. I missed the vote where the Servlet API and JSP classes were going to
>> be stored in the same repo. Is there any way that I can -1 that after the
>> fact?
>>
>> Severa
On Tue, 16 Jul 2002, Jon Scott Stevens wrote:
> Date: Tue, 16 Jul 2002 11:56:40 -0700
> From: Jon Scott Stevens <[EMAIL PROTECTED]>
> Reply-To: Tomcat Developers List <[EMAIL PROTECTED]>
> To: tomcat-dev <[EMAIL PROTECTED]>
> Subject: Missed vote
>
> A
Arg. I missed the vote where the Servlet API and JSP classes were going to
be stored in the same repo. Is there any way that I can -1 that after the
fact?
Several of us have worked hard over the years to completely separate the
Servlet API from the JSP API for various valid reasons (including th
14 matches
Mail list logo
