[ http://issues.apache.org/jira/browse/COCOON-1802?page=comments#action_12370955 ]
Andreas Hochsteger commented on COCOON-1802: -------------------------------------------- I'll try to submit a report tomorrow that shows which blocks can already be built using 'mvn package' after converting with this script. For the failed blocks I'll give a description of the type of failure. > 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 > Attachments: m10n-blocks.zip, m10n-blocks.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 <blockname>... > Example: > # ./m10n-blocks.sh asciiart faces > Conventions > ----------- > The script assumes, that every block will consist of a parent block > (cocoon-<blockname>), an implementation block (cocoon-<blockname>-impl) > and a sample block (cocoon-<blockname>-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
