RE: Struts 2.5

2014-09-17 Thread Martin Gainty
> Date: Wed, 17 Sep 2014 10:20:31 -0400 > Subject: Re: Struts 2.5 > From: davelnew...@gmail.com > To: dev@struts.apache.org > > I'm not excited about keeping the deprecated plugins around; IMO it implies > support. > > People still ask questions about the Dojo plugin on Stack Overflow, running

Re: Struts 2.5

2014-09-17 Thread Paul Benedict
If you move them into a separate module for 2.5, just don't include it in the parent's build process (include it only as a special Maven profile). It's someone is a die-hard hacker and wants to build it themselves, they can. PS: When 3.0 comes around, I recommend we split off all plugins into inde

Re: Struts 2.5

2014-09-17 Thread Dave Newton
I'm not excited about keeping the deprecated plugins around; IMO it implies support. People still ask questions about the Dojo plugin on Stack Overflow, running in S2.3. The plugin must die. On Wed, Sep 17, 2014 at 10:17 AM, Paul Benedict wrote: > Ah, struts-extras... how time comes full circle

Re: Struts 2.5

2014-09-17 Thread Paul Benedict
Ah, struts-extras... how time comes full circle. Struts 1 had its extra package too: http://struts.apache.org/development/1.x/struts-extras/ What does creating the new project buy us? or an end-user? Just curious. Not criticizing; just wanting to learn your plan. Cheers, Paul On Wed, Sep 17, 20

Re: Struts 2.5

2014-09-17 Thread Lukasz Lenart
One more idea: instead of dropping deprecated plugins, move them into a new project ie. struts-extras, so the Struts project will consist of: - struts-framework - struts-examples - struts-apps - struts-archetypes - struts-extras - struts-website (on SVN) As far I can recall there was discussion ab