Dear Wiki user, You have subscribed to a wiki page or wiki category on "Lenya Wiki" for change notification.
The following page has been changed by JörnNettingsmeier: http://wiki.apache.org/lenya/TestDrivingLenya1%2e4-HEAD The comment on the change is: updated to reflect michi's configuration changes ------------------------------------------------------------------------------ === Getting Cocoon === + As of 2006-03-03, Cocoon has been included in the Lenya repository via the SVN "externals" mechanism, i.e. you no longer need to download it separately. - Since 1.4-HEAD is a developer release, the docs are sometimes a little out-of-date. You will need the most recent Cocoon-2.1.x release from SVN, because the release versions do not yet include the javax.jcr package with special code for content repositories. - - There is currently a problem with a broken link on the Cocoon download page, and Antonio Gallardo tells me the snapshots are currently broken. He recommends checking out - {{{ - yourhost:/srv/lenya # svn co http://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/ cocoon_2_1_X - }}} === Configuring the Lenya Build === - First of all, create your own config file: + Under Linux, call the configure script: + {{{ - yourhost:/srv/lenya/lenya_1_4_X # cp build.properties local.build.properties + yourhost:/srv/lenya # ./configure.sh }}} - With your favourite vi, change the value of '''cocoon.src.dir''' to '''../cocoon_2_1_X/'''. Since I want to play with asset uploads, I set '''enable.uploads''' to '''true'''. I won't bother with Tomcat yet - the built-in servlet engine is good enough for testing. - There is no need to build Cocoon manually - the Lenya build process will take care of that. + You will be prompted for some configuration options that are self-explaining. + + FIXME: Windows? === Building === @@ -56, +53 @@ Lenya needs to write to the filesystem to store the pages you create, so you need to do a '''chown -R lenya:lenya /srv/lenya''' now. ''FIXME: this is not good security practice - only the subtree that actually gets written to should be writable for user lenya, not the code. can't test it at the moment, though.'' + ''FIXME: the problem can be alleviated by moving the content directory out of the webapp dir. this feature is currently experimental.'' Start your brand-new, bleeding-edge Lenya with {{{ @@ -71, +69 @@ {{{ yourhost:/srv/lenya # cd lenya_1_4_X yourhost:/srv/lenya/lenya_1_4_X # svn update . - yourhost:/srv/lenya/lenya_1_4_X # cd ../cocoon_2_1_X - yourhost:/srv/lenya/cocoon_2_1_X # svn update . }}} - Then do a '''./build.sh''' in the lenya_1_4_X directory. If you encounter problems during the build, try '''./build.sh clean''' in both the cocoon and lenya trees before you build. Back up your publication data first, just in case. There is an entry in build.properties that tells the build process to leave your content alone when cleaning up, but it might not cover all your modifications. + Then do a '''./build.sh''' in the lenya_1_4_X directory. If you encounter problems during the build, try '''./build.sh clean''' in the lenya tree before you build. Back up your publication data first, just in case. There is an entry in build.properties that tells the build process to leave your content alone when cleaning up, but it might not cover all your modifications. ["RandomThingsLearnedWhilePlayingWith1.4HEAD"] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
