Martin Cooper wrote: > I'm planning on making some other changes to the Struts build process in the > near future, and I could certainly roll these in if people think it would be > desirable.
Here's a different but related issue. For the example applications, I'm wondering if we want to adopt a file system format that allows someone to download and install the WAR, and have all the source code in place, ready for exploration and tweaking. This is the approach I've been taking with my own examples. http://husted.com/struts/resources/struts-simple.zip http://husted.com/scaffolding/dist/logon.zip The source is under WEB-INF (/web-inf/src/java/ ...), and the build process is setup so you can work on it in place, without going through a deployment phase. This would let us offer example, exercise, and documentation WARs, with source, directly from the Web site where people could try them out as pure applications, and take a peek at how things work. If this meshes with Martin's other plans, I could help with the necessary changes. I'm also meaning to relabel "struts-simple" as a workflow example, since that it what it has become. The new logon example (above) also includes using Velocity templates with the nightly build, but doesn't use the latest version of the new Velocity Tools, which is also compatible with Struts 1.0. http://cvs.apache.org/viewcvs/jakarta-velocity-tools/ I've also been working on a new version of the Struts "blank" app, if anyone is interested. http://husted.com/scaffolding/dist/blank.zip Basically the same thing, but with slightly different conventions and (more importantly) a build file that includes options for JavaDocs and building a WAR. I also hope to slip in some kind of stub for unit testing soon, based on some other work I'm doing with Vincent. -- Ted Husted, Husted dot Com, Fairport NY USA. -- Building Java web applications with Struts. -- Tel +1 585 737-3463. -- Web http://www.husted.com/struts/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
