Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 88773 invoked from network); 6 Aug 2008 11:20:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Aug 2008 11:20:46 -0000 Received: (qmail 25433 invoked by uid 500); 6 Aug 2008 11:20:45 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 25357 invoked by uid 500); 6 Aug 2008 11:20:45 -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 25346 invoked by uid 99); 6 Aug 2008 11:20:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Aug 2008 04:20:45 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [88.198.46.98] (HELO indoqa.com) (88.198.46.98) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Aug 2008 11:19:48 +0000 Received: from [10.4.1.227] (unknown [86.59.20.138]) by indoqa.com (Postfix) with ESMTP id CF6E5255ED3 for ; Wed, 6 Aug 2008 13:19:44 +0200 (CEST) Message-ID: <489988C9.2090106@apache.org> Date: Wed, 06 Aug 2008 13:19:37 +0200 From: =?ISO-8859-1?Q?Reinhard_P=F6tz?= User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: [vote] Release of servlet-service-impl-1.1.0, spring-configurator-2.0.0, jnet-1.0.0, block-deployment-1.0.0, cocoon-maven-plugin-1.0.0-M3 X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org I've prepared the artifacts for the release of our four subprojects: Cocoon Servlet-Service Framework Impl 1.1.0 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The most important change is that it doesn't depend on the Cocoon source resolver any more. Custom protocols (e.g. block-context) can still be used by registering them with JNet. Cocoon Spring Configurator 2.0.0 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A major release is necessary because the block deployment functionality was rewritten and moved into the separate Block-Deployment module. Apart from this there have been some minor bug fixes and improvements. Cocoon JNet 1.0.0 ~~~~~~~~~~~~~~~~~ Cocoon JNet allows the dynamic registration of URLStreamHandler factories with your JVM. That's a feature that isn't supported by Java itself. This module was donated to the Apache Commons project and will hopefully be released there sooner or later. That's the first release of this module. Cocoon Block-Deployment 1.0.0 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The Block-Deployment module provides a Java servlet context listener, that unpacks all blocks into the temp directory of the current servlet context. Previously this functionality was part of the Spring Configurator but was considered to be too Cocoon specific. That's the first release of this module. - o - Additionally I've prepared the artifacts for the release of the Cocoon Maven Plugin 1.0.0-M3 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The only difference to M2 is that it was compiled with Spring 2.5.5 because M2 causes some wired exceptions when it is used with Spring >2.5.2. As always, the release of the Cocoon Maven Plugin also makes the release of the cocoon-rcl-webapp-wrapper and cocoon-rcl-spring-reloader necessary. Cocoon Parent POM - Version 7 & Cocoon Tools Modules - Version 7 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In order to use the most recent dependency and plugin versions in the subprojects and the Maven plugin, I had to create a new release of the Cocoon Parent POM and the Cocoon Tools Modules. - o - Currently the proposed artifacts can only be tested either with latest trunk or Corona. For that purpose add a 'cocoon-staging' profile to your Maven settings.xml: cocoon-staging cocoon.staging Cocoon staging repository http://people.apache.org/builds/cocoon cocoon.staging Cocoon staging repository http://people.apache.org/builds/cocoon and use the proposed artifacts instead of SNAPSHOT versions. - o - You can find the staged files for all modules (sources, binaries, javadocs, checksums, gpg signatures) at - http://people.apache.org/builds/cocoon/ (Maven 2 repo) - http://people.apache.org/~reinhard/cocoon-staging/ (Standard release artifacts) SVN tags of all these artifacts can be found at http://svn.apache.org/repos/asf/cocoon/tags/. This majority vote stays open for 72 hours. Please cast your votes. Here is my +1 (after successfully testing with Cocoon trunk and Corona). -- Reinhard P�tz Managing Director, {Indoqa} GmbH http://www.indoqa.com/en/people/reinhard.poetz/ Member of the Apache Software Foundation Apache Cocoon Committer, PMC member reinhard@apache.org ________________________________________________________________________