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" subdirectory to contain this artifact? If > > the business logic turns out to be reusable too, that could go in a > > parallel "mailreader-actions" subdirectory. > > Moving everything over into a "standard" Subversion layout was the right thing to > do, but as we reorganize, we may want to create a top-level directories for each > major release series. Such as: > > /v1/trunk/struts-core > /v1/trunk/struts-faces > /v1/branches > > and > > /v2/trunk/struts-core > /v2/trunk/struts-faces (if we needed such a thing) > /v2/branches > > Since it does look like we will have parallel v2 development and v1 > maintenance/evolution.
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 some people have referred to as v1. I'd certainly not want to see us create version-specific trees until we know that we have a disagreement on whether or not some substantial change (that someone is ready to commit) should be going into the current tree. ;-} -- Martin Cooper > Then, whatever is under the "root" /trunk has not been reorganized yet, and > everything under /v1/trunk has already been reorganized as an artifact. > > Since we have a number of applications knocking around, I would suggest we have an > "applications" or "apps" subproject, that could host all the various examples. So, > we might have something like > > /v1/trunk/apps/struts-blank > /v1/trunk/apps/struts-examples > /v1/trunk/apps/struts-mailreader > /v1/trunk/apps/struts-mailreader-database > /v1/trunk/apps/struts-mailreader-faces > /v1/trunk/apps/struts-mailreader-faces-tiles > /v1/trunk/apps/struts-tiles-examples > > Here, each folder under apps/ would represent a separate artifact that could be > released separately, or bundled with other subprojects to form a product > distribution. (Like the "best available" of everything.) > > Aside from apps/, the other top-level folders under trunk/ might each represent a > separate artifact that could be released separately, such as: > > apps/ > struts-core/ > struts-site/ > struts-bsf/ > struts-el/ > struts-faces/ > struts-scripting/ > struts-taglib/ > > -Ted. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
