Return-Path: Delivered-To: apmail-cocoon-docs-archive@www.apache.org Received: (qmail 71930 invoked from network); 15 Aug 2006 14:36:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Aug 2006 14:36:27 -0000 Received: (qmail 98200 invoked by uid 500); 15 Aug 2006 14:36:27 -0000 Delivered-To: apmail-cocoon-docs-archive@cocoon.apache.org Received: (qmail 98172 invoked by uid 500); 15 Aug 2006 14:36:27 -0000 Mailing-List: contact docs-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: docs@cocoon.apache.org List-Id: Delivered-To: mailing list docs@cocoon.apache.org Received: (qmail 98161 invoked by uid 99); 15 Aug 2006 14:36:27 -0000 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [207.7.158.203] (HELO cocoon.zones.apache.org) (207.7.158.203) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Aug 2006 07:36:27 -0700 Message-ID: <4632843.1155652439349.JavaMail.daisy@cocoon.zones.apache.org> Date: Tue, 15 Aug 2006 14:33:59 +0000 (GMT+00:00) From: daisy@cocoon.zones.apache.org To: docs@cocoon.apache.org Subject: [DAISY] Updated: Releasing Cocoon Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N A document has been updated: http://cocoon.zones.apache.org/daisy/documentation/1199.html Document ID: 1199 Branch: main Language: default Name: Releasing Cocoon (unchanged) Document Type: Cocoon Document (unchanged) Updated on: 8/3/06 8:33:41 PM Updated by: Jorg Heymans A new version has been created, state: publish Parts ===== Content ------- This part has been updated. Mime type: text/xml (unchanged) File name: (unchanged) Size: 3505 bytes (previous version: 3000 bytes) Content diff: (53 equal lines skipped)

If the "-N" option doesn't work for you, you have to comment the modules section in the pom by hand and comment it out after the release.

+++

Take care to manually change all poms that have the released pom as a parent. +++ For example you release cocoon-blocks-modules under version 3, before it was +++ 2-SNAPSHOT. The next version increment of that pom is thus 3-SNAPSHOT, and you +++ should manually change all poms that have 2-SNAPSHOT for this parent to +++ 3-SNAPSHOT. Otherwise the trunk build will use "old" ie already released +++ artifacts, which is not desired.

+++

Releasing JAR artifacts

mvn -Dusername=[svn-user-name] -Dpassword=******** release:perform
if SNAPSHOT dependencies have been replaced before, point again to them
Point all artifacts in trunk to the new snapshot version of this artifact. +++

Note (jheymans)

(21 equal lines skipped)