Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 75964 invoked from network); 17 Aug 2008 13:53:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Aug 2008 13:53:42 -0000 Received: (qmail 78031 invoked by uid 500); 17 Aug 2008 13:53:40 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 77942 invoked by uid 500); 17 Aug 2008 13:53:40 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 77931 invoked by uid 99); 17 Aug 2008 13:53:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Aug 2008 06:53:40 -0700 X-ASF-Spam-Status: No, hits=-1.0 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of grek@tuffmail.com designates 216.86.168.178 as permitted sender) Received: from [216.86.168.178] (HELO mxout-03.mxes.net) (216.86.168.178) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Aug 2008 13:52:43 +0000 Received: from [192.168.1.214] (unknown [217.116.183.178]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 5A22623E49A for ; Sun, 17 Aug 2008 09:53:11 -0400 (EDT) Message-ID: <48A82D2D.5030504@tuffmail.com> Date: Sun, 17 Aug 2008 15:52:45 +0200 From: Grzegorz Kossakowski User-Agent: Thunderbird 2.0.0.12 (X11/20071114) MIME-Version: 1.0 To: Cocoon's dev mailing list Subject: Next releases of JNet, SSF and blockdeployment Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, There was a problem (COCOON-2236[1]) discovered with refactored release of Servlet Service Framework that made it incompatible with Cocoon Core 2.2.0. Since this issue is already closed it makes sense to prepare next minor release of SSF. Additionally, both JNet and blockdeployment have to be released. Therefore I would propose to release following versions: 1. cocoon-jnet:1.1.0 (there are new methods introduced) 2. cocoon-blockdeployment:1.1.0 (there is an interface moved from SSF and implementation for it) 1. cocoon-servlet-service-impl:2.1.0 (because this module depends on JNet 1.1.0) When all these three artifacts being used, Cocoon Core 2.2.0 should work just fine. Reinhard, I remember that you have already offered to help with this. Is this offer still relevant? [1] https://issues.apache.org/jira/browse/COCOON-2236 -- Grzegorz Kossakowski