struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brian Pontarelli <br...@pontarelli.com>
Subject Re: Let's kill xwork (was Re: 2.1.8 release?)
Date Tue, 11 Aug 2009 16:55:56 GMT

On Aug 10, 2009, at 11:52 PM, Don Brown wrote:

> On Tue, Aug 11, 2009 at 3:38 PM, Paul Benedict<pbenedict@apache.org>  
> wrote:
>> On Tue, Aug 11, 2009 at 12:22 AM, Don Brown  
>> <donald.brown@gmail.com> wrote:
>>
>>> By forking XWork, we can a) bring core Struts 2 code into the  
>>> project
>>> where it belongs and b) still leave it available for other users in
>>> OpenSymphony.
>>>
>>>
>> If you fork XWork, it obviously won't be XWork anymore. If that's  
>> what you
>> want to do to cut the apron strings, then I can agree to that.  
>> However, I
>> thought you guys were saying you actually want to make Apache *OWN*  
>> XWork.
>> That's something completely different and am against. If the code  
>> is copied
>> into Struts as fork, the whole XWork branding should wash away and  
>> Struts
>> should have no more reference to "xwork" anywhere.
>
> Awesome - that is exactly what I'm saying.  Kill it with fire! :)

Oh yeah! Burn baby burn!

Maybe its time to branch Struts core, drop in xwork, refactor the heck  
out of it, and call it struts 3. Code name the release "Phoenix". :)

-bp


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Mime
View raw message