Thanks, Wendy. I've had to spend some of my volunteer hours elsewhere lately, but things should be getting back on track for me now. I'm planning to work on the Applications/MailReader project next, and then get back to the Core documentation.
We've always had troubles with the tiles-documentation webapp. Overall, I would suggest that we * Make the MailReader a true best-practices application, including the use of Tiles. * Add the Struts Cookbook. * See if we can move some of the content of tiles-documentation into the Cookbook. * Also see if the struts-examples content can be moved to the cookbook, so that maybe we can get the webapps down to blank, cookbook, exercises, and mailreader. (Plus whatever Shale and standalone Tiles want to do.) If in the meantime, we want to consider moving tiles-documentation into the sandbox, until it can be repaired, refactored, or disbursed into other applications. I haven't looked at EL, but it might be the same situation: Programming examples that we are trying to carry in a solo app might be better handled by the Cookbook. -Ted. On 10/3/05, Wendy Smoak <[EMAIL PROTECTED]> wrote: > The usual Monday update. :) > > The tiles-documentation webapp now builds and (mostly) works, but it's not > included in the overall 'build-all' goal. Right now it lives in > tiles/tiles-documentation, and I don't immediately see how to get Maven to > build it as part of Tiles. > > There's a similar situation (a jar plus a webapp) in EL, but that's not done > quite right either-- there you have to convince Maven to include a second > directory of source code, which it doesn't like to do. Both Tiles and EL > probably need to be reorganized to work better with Maven. > > The Cactus tests for EL still need attention. I'll open a bug ticket for it > in a few days. > > -- > Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
