Yes that was the latest version. I've just updated it for 1.3.
I still need to update the license and make it build with Maven.
If there are no objections, I'll check it in as /apps/cookbook later
this evening.
As long as it doesn't jeopardize my emeritus status ;-)
Steve
Ted Husted wrote:
---------- Forwarded message ----------
From: James Mitchell <[EMAIL PROTECTED]>
Date: Sep 12, 2005 3:48 PM
Subject: Re: Blank build broken?
To: Struts Developers List <dev@struts.apache.org>
I think this is a great idea. So the zip on that page is the latest
of those sources? Or are they on sf.net?
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
Yahoo: jmitchtx
MSN: [EMAIL PROTECTED]
Skype: callto://jmitchtx
On Sep 11, 2005, at 2:18 PM, Ted Husted wrote:
I'd been thinking that Apps should be a multiproject of its own, so as
James says, we can host multiple applications and multiple version of
applications.
When the apps we have are stabalized, I'd like to bring Steve
Raeburn's Struts Cookbook into the distribution.
* http://www.ninsky.com/struts/index.html
Steve's working on other things right now, but he would be happy to
contribute the Cookbooks application, as he always intended, once we
have a place to park it.
(If someone is looking for something to do, snag the Cookbook source
and refactor it for Maven.)
Having a Cookbook at hand means we won't have to try and stretch the
MailReader to demonstrate different techniques. I'd like to make the
MailReader a true best-practices application with no extra fluff.
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.
It would also be fun to extend the mailreader-dao so that we could
plugin Hibernate and iBATIS implementation, ideally without any of the
Mailreader web apps knowing the difference.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
