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 ------------------------------------------------------------------------------ When I asked whether it would be safe and sane to adopt 1.4 for a project that is due by christmas 2005 (and indicated my willingness to deal with the occasional problem or rough edge), GregorRothfuss said: ''"the data should stay pretty stable, while the code might not. recently, a jcr import usecase was added that might help with future migration scenarios. with your deadlines, i would strongly recommend 1.4."'' - Ok. Here we go. + Well, it's two months later now, and 1.4 is nowhere near a release (although pretty usable), but here we go :) == Prerequisites == @@ -20, +20 @@ === Getting Lenya === First, you need to check out the latest source code of Lenya-1.4: - + {{{ yourhost:/srv/lenya # svn co http://svn.apache.org/repos/asf/lenya/trunk lenya_1_4_X - + }}} (Check the "official" SVN documentation at http://lenya.apache.org/1_4/installation/subversion.html in case the procedure changes) === Getting Cocoon === @@ -30, +30 @@ 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: - + {{{ yourhost:/srv/lenya/lenya_1_4_X # cp build.properties local.build.properties - + }}} 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. @@ -48, +49 @@ ''For SUSE users: something in the global SUSE ant configuration conflicts with the Lenya build process. You will see errors like "undefined <if>-macro" (for Lenya 1.2.x) or "undefined option '-cp'" (happens with Lenya 1.4.x). To work around this problem, use the --noconfig option (which prevents ant from reading the config files in /etc and ~/.'' Now all that's left to do is - + {{{ yourhost:/srv/lenya/lenya_1_4_X # ./build.sh - + }}} Grab a coffee while it compiles. 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.'' Start your brand-new, bleeding-edge Lenya with - + {{{ yourhost:/srv/lenya/lenya_1_4_X # su -c "./lenya.sh servlet" lenya - + }}} Surf to yourhost:8888 and enjoy. Remember to repeat this procedure at least once a week, lest the bleeding edge effect wear off :-D @@ -67, +68 @@ === Updating and rebuilding === After the initial svn checkout, updates are very fast. Just do - + {{{ 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. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
