Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tapestry Wiki" for change notification.
The following page has been changed by ErikVullings: http://wiki.apache.org/tapestry/BuildingTapestry ------------------------------------------------------------------------------ + ## page was renamed from BuildingTapestry31 - Tapestry 3.1 is now well under way ... but there's the question of building it. + Tapestry 4.0 is now well into beta ... but there's the question of building it. A set of Ant build files was created for HiveMind, called "HiveBuild". They are designed to be reasonably reused; that's what Tapestry does. - At this point, Tapestry 3.1 is in alpha, and needs HiveMind 1.1-alpha code as well. We're on the bleeding edge. + At this moment, Tapestry builds against HiveMind 1.1-beta-3. You will need to get HiveMind from http://jakarta.apache.org/site/downloads/downloads_hivemind.cgi - You need to get from CVS two project directories, one for the jakarta-hivemind module, one for the jakarta-tapestry module. + You also need Ant 1.6.2 and JDK 1.5. You also need to download ant install Apache Forrest from http://xml.apache.org/forrest/ (latest from trunk, i.e. 0.8-dev, works fine). + Before building Tapestry, you must tell Tapestry's build scripts where the HiveBuild scripts (from HiveMind are). - You also need Ant 1.6.2. - - Build HiveMind (ant install). Ant will automatically download various dependencies from the Maven repository on ibiblio. You might have to run it a couple of times, dependending on what it has to download (it has to stop after copying files into Ant's lib directory). Inside jakarta-tapestry/config create a build.properties file: {{{ @@ -19, +18 @@ Adjust the path as necessary. It must be the absolute path to the hivebuild directory. - Create the directory jakarta-tapestry/ext-package/lib + From the jakarta-tapestry directory, you should be able to build ('''ant install'''). Nearly all intermediate files (such as compiled class files) are copied into + ''tempdir''/tapestry ... typically C:/WINDOWS/TEMP/tapestry. Ant will automatically download various dependencies from the Maven repository on ibiblio. You might have to run it a couple of times, dependending on what it has to download (it has to stop after copying certain libraries into Ant's lib directory). - Copy the HiveMind libraries there, i.e., from jakarta-hivemind: - {{{ - cp target/*.jar ../jakarta-tapestry/ext-package/lib - }}} - From the jakarta-tapestry directory, you should be able to build (ant install). + After an install you can build documentation ('''ant site'''). This does three things: + * Copies Forrest xdoc files (and etc.) to target/forrest-composite + * Runs Javadoc, clover and other reports, generating into ''tempdir''/tapestry/target/docs + * Runs Forrest, to create all the HTML files, which end up in ''tempdir''/tapestry/target/docs + After building the site target the ''first time'', if you just change some xdoc documentation, you can use the target '''fast-site'''. That skips the middle step, which is much faster (a few seconds for the copy, about a minute to run Forrest). - After an install you can build documentation (ant site). This does three things: - * Copies Forrest xdoc files (and etc.) to target/forrest-composite - * Runs Javadoc, clover and other reports, generating into target/docs - * Runs Forrest, to create all the HTML files, which end up in target/docs - After building the site target the first time, if you just change some xdoc documentation, you can use the target fast-site. That skips the middle step, which is much faster (a few seconds for the copy, about a minute to run Forrest). + In addition, after building the site the first time, you can use the '''live-site''' target. This is very powerful ... it starts up Jetty and Cocoon and runs the Tapestry site '''live!'''. You can access the live site via http://localhost:8888. - Don't fear ... this process will improve. Eventually, Tapestry will be stable, HiveMind will be stable, the HiveMind libraries will be up at ibiblio and this whole process will be nice. It's already better than Tapestry 3.0's kludgey build system. + When you make changes to source XML files (including site.xml and tabs.xml), you execute (in a new window) '''ant copy-documentation-to-composite''', at which point, the changes will be visible to the live site. This makes it very, very quick and easy to make small changes and see them almost immediately --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
