On 9/22/05, Ted Husted <[EMAIL PROTECTED]> wrote: > On Sep 11, 2005, at 2:18 PM, Ted Husted wrote (on Struts Dev): > > My thinking is that each application should be separate, with it's own > > Maven build, and no shared code between web applications. Though, the > > MailReader applications could share a business backend, again with its > > own Maven build and unit tests. > > > > In this vision, we'd have something like > > > > /apps > > - blank > > - cookbook > > - examples > > - mailreader-classic > > - mailreader-chain > > - mailreader-dao <- business classes > > - mailreader-shale > > - mailreader-ti > > > > This might then encourage other mailreader implementations to help > > introduce developers to new technologies, like AjaxTags, Dialogs, and > > FormDef, for example. > > On 9/20/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote: > > Considering Ted's initiative to create more different implementations > > of venerable MailReader and his invitation of non-committeres to > > participate, I converted MailReader from standard Struts using Struts > > Dialogs. > > > > Here it is: http://www.superinterface.com/mailreader > > How about if we start a new SourceForge project for alternative > MailReaders? I'd still like to do one for FormDef, for example, but I > don't want to saddle the Apache team with too many MailReader > implementations. :)
I knew that adding my implementation of MailReader (along with Struts Dialogs library) into main Struts trunk was too good to be true... Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
