Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 47970 invoked from network); 3 Dec 2008 21:05:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Dec 2008 21:05:07 -0000 Received: (qmail 10490 invoked by uid 500); 3 Dec 2008 21:05:18 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 10365 invoked by uid 500); 3 Dec 2008 21:05:17 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 10354 invoked by uid 99); 3 Dec 2008 21:05:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Dec 2008 13:05:17 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jgawor@gmail.com designates 74.125.44.29 as permitted sender) Received: from [74.125.44.29] (HELO yx-out-2324.google.com) (74.125.44.29) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Dec 2008 21:03:49 +0000 Received: by yx-out-2324.google.com with SMTP id 3so2066249yxj.85 for ; Wed, 03 Dec 2008 13:04:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=FK29l1QxRloRl1F4KTypLgjJT6Gt8rgcjKTJPSIL/9Q=; b=nAD7pBkcv8nPKwE+ZtwaOERkKKRV/+e2+3x9Uud0Oy1hWJRwvYLxFHC/tSWFenStYB 8AJVDKnawJeQvqXrdyO+P7Uv1d9gcA2nLovVWAgUsD/eh8/OcSkCRzIdExKYGrVDChtn 9uT9N9i3uvBTLIAFkq/jhr596SgKaHQeLxL7A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=m9l8yRUggmF6L8eNyjykHS7J/xmy/BRLHqL/fskvLgRo0flI6C+oGCJBk93ORJ9wRF R96GJJ5rnxpiTcojpeAQv6YxKAeM7HMlzc+JHRvJWkWDCj9XkpgJjaXnZIyN4FvTTHjt +5gzR6qXFrLeUHVhmpfjtojOGQsbSj5MUkiYA= Received: by 10.65.97.18 with SMTP id z18mr13360123qbl.11.1228338266409; Wed, 03 Dec 2008 13:04:26 -0800 (PST) Received: by 10.65.122.10 with HTTP; Wed, 3 Dec 2008 13:04:26 -0800 (PST) Message-ID: <5eb405c70812031304p51bd3dcejec5785261d5b3611@mail.gmail.com> Date: Wed, 3 Dec 2008 16:04:26 -0500 From: "Jarek Gawor" To: dev@geronimo.apache.org Subject: Re: servlet 3.0 spec in 2.2 In-Reply-To: <4936E829.4060907@earthlink.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4936E829.4060907@earthlink.net> X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Dec 3, 2008 at 3:12 PM, Joe Bohn wrote: > Things looks strange regarding the servlet spec references in 2.2. > > We include dependency management entries for both 3.0 & 2.5. That much is > fine. > > Nearly everything that references the servlet spec includes the 2.5 version > with the exception of the following: > - jee-specs - This is the most confusing to me. I was expecting that either > 2.5 would be included or both 2.5 & 3.0 (if that is even possible). Why > 3.0? > - jaxws-tests/jaxws-rest-war - Jarek indicated that this might just have > been a bad cut/paste and it should be fine with the 2.5 spec. > - jaxws-wsa-tests/wsa-test-war - same as above. > > So, the question is ... Should we move jee-specs to use the 2.5 spec and > then remove the references to the servlet_3.0 spec until after the 2.2 > server is released? Yes. I don't think we will pass Java EE 5 TCK otherwise. Or we can do the trick like we do for the connector spec. Jarek