Return-Path: Delivered-To: apmail-struts-dev-archive@www.apache.org Received: (qmail 8463 invoked from network); 28 Dec 2009 19:38:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 28 Dec 2009 19:38:09 -0000 Received: (qmail 11425 invoked by uid 500); 28 Dec 2009 19:38:08 -0000 Delivered-To: apmail-struts-dev-archive@struts.apache.org Received: (qmail 11370 invoked by uid 500); 28 Dec 2009 19:38:08 -0000 Mailing-List: contact dev-help@struts.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Struts Developers List" Reply-To: "Struts Developers List" Delivered-To: mailing list dev@struts.apache.org Received: (qmail 11357 invoked by uid 99); 28 Dec 2009 19:38:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Dec 2009 19:38:08 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.221.185] (HELO mail-qy0-f185.google.com) (209.85.221.185) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Dec 2009 19:38:00 +0000 Received: by qyk15 with SMTP id 15so4517742qyk.23 for ; Mon, 28 Dec 2009 11:37:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.1.139 with SMTP id 11mr6690666qcf.2.1262029059488; Mon, 28 Dec 2009 11:37:39 -0800 (PST) In-Reply-To: References: <16d6c6200912271025p74b4c2eeoeb87e20e60f3675b@mail.gmail.com> <9f960bad0912271118h3b98e12crbd6131c9fc5e5edd@mail.gmail.com> <16d6c6200912271239n431c178ag93cf78d399d69637@mail.gmail.com> <16d6c6200912281057l4e102f6g9401a0f12a202333@mail.gmail.com> <4B3901C9.2050400@Newfield.org> Date: Mon, 28 Dec 2009 14:37:39 -0500 Message-ID: Subject: Re: XWork has landed! From: Wes Wannemacher To: Struts Developers List Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Mon, Dec 28, 2009 at 2:16 PM, Paul Benedict wrote: > Having XWork as a separate module is actually preferred, but only > because it's a better design decision. It will create a clear > separation of concerns within the code base. Now with that said, XWork > should be a *child* module of Struts -- not a separate release. > > Paul When you (and Martin) are indicating a "child" of Struts, I assume you mean for it to be a child outside of Struts2. I am a team player and I'm willing to set it up, whatever the consensus, but I would really prefer for it to be a child of Struts2. I understand the implications of supporting it, etc. But, the biggest gripe (and *my* motivation for voting to move it over) is that we often wait to release Struts2 because we need a release of XWork. Not to knock Rainer, but sometimes this process takes a while. If it is a part of the Struts2 umbrella, then the release process outlined in the wiki will still apply, but everything (including xwork artifacts) will go out at once. Plus, one of my tasks for Struts 2.2 is to take advantage of maven's dependencyManagement and pluginManagement. We could probably work that into the struts-master, but I hate to push changes to Struts 1, since I don't use it much. I would just like to balance making our lives easier against other factors. In the end, if we make managing this beast easier we can move on things faster. I know that "fast" isn't necessarily a goal, but I'd still like to try to get to KISS so that potential patch-makers aren't so intimidated by our code and build process. -Wes -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org For additional commands, e-mail: dev-help@struts.apache.org