On Wed, 2004-10-13 at 23:18, Martin Cooper wrote:
On Wed, 13 Oct 2004 06:26:00 -0400, Ted Husted [EMAIL PROTECTED] wrote:
On Tue, 12 Oct 2004 15:22:38 -0700, Martin Cooper wrote:
That said, I would really like to see us all stick together for as
long as possible, and not diverge into 1.x
On Tue, 12 Oct 2004 15:22:38 -0700, Martin Cooper wrote:
That said, I would really like to see us all stick together for as
long as possible, and not diverge into 1.x and 2.x paths too soon,
simply because I don't think there is enough energy here to sustain
two parallel version of Struts.
On Wed, 13 Oct 2004 06:26:00 -0400, Ted Husted [EMAIL PROTECTED] wrote:
On Tue, 12 Oct 2004 15:22:38 -0700, Martin Cooper wrote:
That said, I would really like to see us all stick together for as
long as possible, and not diverge into 1.x and 2.x paths too soon,
simply because I don't think
On Tue, 12 Oct 2004 06:40:38 -0400, Ted Husted [EMAIL PROTECTED] wrote:
On Mon, 11 Oct 2004 21:38:26 -0700, Martin Cooper wrote:
At this point, I'm not sure we all agree on what would constitute a
part of v2 rather than v1, since I anticipate some fairly
substantial changes going into what
On Sun, 10 Oct 2004 23:25:06 -0400, Ted Husted [EMAIL PROTECTED] wrote:
On Sun, 10 Oct 2004 13:22:27 -0700, Craig McClanahan wrote:
Splitting out the database part of mailreader seems like an obvious
first step. How about a top level examples directory with a
mailreader-database
On Sun, 10 Oct 2004 08:29:20 -0400, Ted Husted [EMAIL PROTECTED] wrote:
On Sat, 09 Oct 2004 21:06:44 -0700, Craig McClanahan wrote:
... Interestingly, this subproject has four subsubprojects ...
Are you counting the MailReader database as a separate artifact?
I hadn't been, and that
On Sun, 10 Oct 2004 13:22:27 -0700, Craig McClanahan wrote:
Splitting out the database part of mailreader seems like an obvious
first step. How about a top level examples directory with a
mailreader-database subdirectory to contain this artifact? If
the business logic turns out to be
I've taken advantage of the new capabilities that Subversion provides
for refactoring, to set up struts-faces as a top-level subproject with
the ability to create its own release artifact. Interestingly, this
subproject has four subsubprojects that provide its content as well,
so the top-level
