Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 14729 invoked from network); 23 Mar 2006 23:27:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 23 Mar 2006 23:27:43 -0000 Received: (qmail 30070 invoked by uid 500); 23 Mar 2006 23:27:42 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 29987 invoked by uid 500); 23 Mar 2006 23:27:41 -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 29976 invoked by uid 99); 23 Mar 2006 23:27:41 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Mar 2006 15:27:41 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Mar 2006 15:27:41 -0800 Received: from ajax (localhost.localdomain [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 0DBA4D4A01 for ; Thu, 23 Mar 2006 23:27:20 +0000 (GMT) Message-ID: <1209016283.1143156440053.JavaMail.jira@ajax> Date: Thu, 23 Mar 2006 23:27:20 +0000 (GMT) From: "Andreas Hochsteger (JIRA)" To: dev@cocoon.apache.org Subject: [jira] Updated: (COCOON-1802) Script for m10n of old blocks In-Reply-To: <891746646.1142677978913.JavaMail.jira@ajax> 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 [ http://issues.apache.org/jira/browse/COCOON-1802?page=all ] Andreas Hochsteger updated COCOON-1802: --------------------------------------- Attachment: svn-reorganize.zip This update contains the following changes: * Renamed ZIP file to svn-reorganize.zip since it better says what it does * Renamed conversion script from m10n-blocks.sh to convert-blocks.sh * Added new script svn-reorganize-trunk.sh which generates the svn commands for the moves using a config file * Adapted to new repository layout suggested by Reinhard * Create new POM in directory 'blocks' which contains all converted blocks as Maven modules * Updated sections Questions and TODOs in README.txt (Please check these - I need some help here!) > Script for m10n of old blocks > ----------------------------- > > Key: COCOON-1802 > URL: http://issues.apache.org/jira/browse/COCOON-1802 > Project: Cocoon > Type: New Feature > Components: - Build System: Maven > Versions: 2.2-dev (Current SVN) > Reporter: Andreas Hochsteger > Assignee: Reinhard Poetz > Attachments: m10n-blocks.zip, m10n-blocks.zip, m10n-blocks.zip, m10n-blocks.zip, svn-reorganize.zip > > See thread starting with http://www.mail-archive.com/dev@cocoon.apache.org/msg42233.html for discussion details. > Here's the info from the file README.txt: > What is it? > ----------- > m10n-blocks.sh is a script which automates parts of the conversion from the > "old" blocks to the "new" mavenized ones. > Configuration > ------------- > Only 2 variables have to be adjusted: > blksrc: > Local directory where https://svn.apache.org/repos/asf/cocoon/blocks is checked out > blkdest: > Local directory where https://svn.apache.org/repos/asf/cocoon/trunk is checked out > Usage > ----- > # ./m10n-blocks.sh ... > Example: > # ./m10n-blocks.sh asciiart faces > Conventions > ----------- > The script assumes, that every block will consist of a parent block > (cocoon-), an implementation block (cocoon--impl) > and a sample block (cocoon--sample). > TODOs > ----- > The subversion commands are currently untested and commented-out. > The implementation pom has to be manually merged with the original pom of the > "old" block. In many cases it is enough to add the dependencies. > The build section should not be merged, since the new directory structure uses > maven defaults and thus doesn't need a special configuration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira