You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Lukasz Lenart <lu...@apache.org> on 2013/04/18 08:00:27 UTC
Re: Plan for Struts 3
A new plan :D
Plan for Struts 2.5:
Request Git repo from INFRA
Import project
Remove deprecated plugins
Drop support for Struts 1 (remove plugin)
Remove deprecated APIs
Switch to Java 1.6
Rename XWork packages to org.apache.struts.xwork
Prepare the first release
Plan for Struts 3:
Rename Struts 2 packages to org.apache.struts
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Plan for Struts 3
Posted by Christian Grobmeier <gr...@gmail.com>.
Just read through it (slowly catching up with e-mails, sorry for all
struts related delays).
Looks good to me and the clean up of the website will be a great step
forwards. I always found it very confusing
Cheers!
On Sat, May 25, 2013 at 1:19 PM, Lukasz Lenart <lu...@apache.org> wrote:
> I have added a point about Website cleanup with some explanation:
>
> https://cwiki.apache.org/confluence/display/WW/Struts+Next
>
> I thought we will be able to start with plan soon but right now the
> main obstacle are recently discovered security vulnerabilities :\
> Anyway, the plan is still valid :-)
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> 2013/5/16 Lukasz Lenart <lu...@apache.org>:
>> The plan updated again :-)
>> https://cwiki.apache.org/confluence/display/WW/Struts+Next
>>
>> Anyway I would like to stabilise the current 2.3.x branch, solve
>> security issue in pipeline and then start with the plan :-)
>>
>>
>> Regards
>> --
>> Łukasz
>> + 48 606 323 122 http://www.lenart.org.pl/
>>
>> 2013/4/26 Lukasz Lenart <lu...@apache.org>:
>>> 2013/4/18 Paul Benedict <pb...@apache.org>:
>>>> I know it's a bit contentious, but I would really like the package name to
>>>> be org.apache.struts3 so that people migrate from struts 1 progressively. i
>>>> am actually in the process of doing this now with struts 2.3 (1000 some
>>>> actions) and it's a life-saver. It will take several years in our team's
>>>> product life cycle to complete the transition.
>>>
>>> Right now we should focus on Struts 2.5, what will be in scope of
>>> Struts 3 time shows ;-)
>>>
>>> Anyway, I would like to drop com.opensymphony.xwork2 package and used
>>> at least org.apache.struts2.xwork2 instead.
>>>
>>>
>>> Regards
>>> --
>>> Łukasz
>>> + 48 606 323 122 http://www.lenart.org.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
--
http://www.grobmeier.de
https://www.timeandbill.de
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Plan for Struts 3
Posted by Lukasz Lenart <lu...@apache.org>.
I have added a point about Website cleanup with some explanation:
https://cwiki.apache.org/confluence/display/WW/Struts+Next
I thought we will be able to start with plan soon but right now the
main obstacle are recently discovered security vulnerabilities :\
Anyway, the plan is still valid :-)
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2013/5/16 Lukasz Lenart <lu...@apache.org>:
> The plan updated again :-)
> https://cwiki.apache.org/confluence/display/WW/Struts+Next
>
> Anyway I would like to stabilise the current 2.3.x branch, solve
> security issue in pipeline and then start with the plan :-)
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> 2013/4/26 Lukasz Lenart <lu...@apache.org>:
>> 2013/4/18 Paul Benedict <pb...@apache.org>:
>>> I know it's a bit contentious, but I would really like the package name to
>>> be org.apache.struts3 so that people migrate from struts 1 progressively. i
>>> am actually in the process of doing this now with struts 2.3 (1000 some
>>> actions) and it's a life-saver. It will take several years in our team's
>>> product life cycle to complete the transition.
>>
>> Right now we should focus on Struts 2.5, what will be in scope of
>> Struts 3 time shows ;-)
>>
>> Anyway, I would like to drop com.opensymphony.xwork2 package and used
>> at least org.apache.struts2.xwork2 instead.
>>
>>
>> Regards
>> --
>> Łukasz
>> + 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Plan for Struts 3
Posted by Lukasz Lenart <lu...@apache.org>.
The plan updated again :-)
https://cwiki.apache.org/confluence/display/WW/Struts+Next
Anyway I would like to stabilise the current 2.3.x branch, solve
security issue in pipeline and then start with the plan :-)
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2013/4/26 Lukasz Lenart <lu...@apache.org>:
> 2013/4/18 Paul Benedict <pb...@apache.org>:
>> I know it's a bit contentious, but I would really like the package name to
>> be org.apache.struts3 so that people migrate from struts 1 progressively. i
>> am actually in the process of doing this now with struts 2.3 (1000 some
>> actions) and it's a life-saver. It will take several years in our team's
>> product life cycle to complete the transition.
>
> Right now we should focus on Struts 2.5, what will be in scope of
> Struts 3 time shows ;-)
>
> Anyway, I would like to drop com.opensymphony.xwork2 package and used
> at least org.apache.struts2.xwork2 instead.
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Plan for Struts 3
Posted by Lukasz Lenart <lu...@apache.org>.
2013/4/18 Paul Benedict <pb...@apache.org>:
> I know it's a bit contentious, but I would really like the package name to
> be org.apache.struts3 so that people migrate from struts 1 progressively. i
> am actually in the process of doing this now with struts 2.3 (1000 some
> actions) and it's a life-saver. It will take several years in our team's
> product life cycle to complete the transition.
Right now we should focus on Struts 2.5, what will be in scope of
Struts 3 time shows ;-)
Anyway, I would like to drop com.opensymphony.xwork2 package and used
at least org.apache.struts2.xwork2 instead.
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Plan for Struts 3
Posted by Paul Benedict <pb...@apache.org>.
I know it's a bit contentious, but I would really like the package name to
be org.apache.struts3 so that people migrate from struts 1 progressively. i
am actually in the process of doing this now with struts 2.3 (1000 some
actions) and it's a life-saver. It will take several years in our team's
product life cycle to complete the transition.
On Thu, Apr 18, 2013 at 1:00 AM, Lukasz Lenart <lu...@apache.org>wrote:
> A new plan :D
>
> Plan for Struts 2.5:
> Request Git repo from INFRA
> Import project
> Remove deprecated plugins
> Drop support for Struts 1 (remove plugin)
> Remove deprecated APIs
> Switch to Java 1.6
> Rename XWork packages to org.apache.struts.xwork
> Prepare the first release
>
> Plan for Struts 3:
> Rename Struts 2 packages to org.apache.struts
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: Plan for Struts 3
Posted by Lukasz Lenart <lu...@apache.org>.
Good point!
Plan for Struts 2.5:
Request Git repo from INFRA
Import project
Remove deprecated plugins
Drop support for Struts 1 (remove plugin)
Remove deprecated APIs
Switch to Java 1.6
Prepare the first release
Plan for Struts 3:
Rename XWork packages to org.apache.struts.xwork
Rename Struts 2 packages to org.apache.struts
Switch to Java 1.7
https://cwiki.apache.org/confluence/display/WW/Struts+Next
2013/4/18 Rene Gielen <re...@gmail.com>:
> Am 18.04.13 08:00, schrieb Lukasz Lenart:
>> A new plan :D
>>
>> Plan for Struts 2.5:
>> Request Git repo from INFRA
>> Import project
>> Remove deprecated plugins
>> Drop support for Struts 1 (remove plugin)
>> Remove deprecated APIs
>> Switch to Java 1.6
>> Rename XWork packages to org.apache.struts.xwork
>> Prepare the first release
>>
>> Plan for Struts 3:
>> Rename Struts 2 packages to org.apache.struts
>
> What is the added value to expect Struts users to go through the pain of
> package renaming two times within a foreseeable time period?
>
> How about this big picture:
> 2.5 - intermediate step requiring users to cleanup their projects -
> switch to Git, remove all deprecated stuff, switch to J6
> 3.0 - new features and API with added value for users to switch to new
> API - includes alignment of all package names
>
> Regarding adoption I'm pretty sure that J6 should still be the way to
> go. J7 adoption seems to be around 15% right now as I read lately, maybe
> the next year helps to increase this rate. At least for 2.5 and start of
> development on 3.0 we should stay with J6 *sigh*
>
>>
>>
>> Regards
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Plan for Struts 3
Posted by Rene Gielen <re...@gmail.com>.
Am 18.04.13 08:00, schrieb Lukasz Lenart:
> A new plan :D
>
> Plan for Struts 2.5:
> Request Git repo from INFRA
> Import project
> Remove deprecated plugins
> Drop support for Struts 1 (remove plugin)
> Remove deprecated APIs
> Switch to Java 1.6
> Rename XWork packages to org.apache.struts.xwork
> Prepare the first release
>
> Plan for Struts 3:
> Rename Struts 2 packages to org.apache.struts
What is the added value to expect Struts users to go through the pain of
package renaming two times within a foreseeable time period?
How about this big picture:
2.5 - intermediate step requiring users to cleanup their projects -
switch to Git, remove all deprecated stuff, switch to J6
3.0 - new features and API with added value for users to switch to new
API - includes alignment of all package names
Regarding adoption I'm pretty sure that J6 should still be the way to
go. J7 adoption seems to be around 15% right now as I read lately, maybe
the next year helps to increase this rate. At least for 2.5 and start of
development on 3.0 we should stay with J6 *sigh*
>
>
> Regards
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Plan for Struts 3
Posted by Lukasz Lenart <lu...@apache.org>.
2013/4/18 Johannes Geppert <jo...@apache.org>:
> Hi,
>
>> Switch to Java 1.6
> when starting a new major release why not start with Java 7?
> I mean Java 6 is already in the end of life cycle. :-)
Good question :-) But I think there are users which migrated to Java 6
already and they don't have a plans to migrate to Java 7 asap (read
corporations, banks, etc).
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Plan for Struts 3
Posted by "info@flyingfischer.ch" <in...@flyingfischer.ch>.
...should have said projects instead of code ;-)
Markus Fischer
Am 18.04.2013 08:58, schrieb info@flyingfischer.ch:
> There is a lot of code out there still relying on Java 6.
>
> If there is no urgent need to use Java 7, it is no good idea to make the
> framework dependent on Java 7:
>
> We should keep a minimal backward compatibility regarding Java.
>
> Markus Fischer
>
> Am 18.04.2013 08:46, schrieb Johannes Geppert:
>> Hi,
>>
>>> Switch to Java 1.6
>> when starting a new major release why not start with Java 7?
>> I mean Java 6 is already in the end of life cycle. :-)
>>
>> Johannes
>>
>> #################################################
>> web: http://www.jgeppert.com
>> twitter: http://twitter.com/jogep
>>
>>
>>
>> 2013/4/18 Lukasz Lenart <lu...@apache.org>
>>
>>> A new plan :D
>>>
>>> Plan for Struts 2.5:
>>> Request Git repo from INFRA
>>> Import project
>>> Remove deprecated plugins
>>> Drop support for Struts 1 (remove plugin)
>>> Remove deprecated APIs
>>> Switch to Java 1.6
>>> Rename XWork packages to org.apache.struts.xwork
>>> Prepare the first release
>>>
>>> Plan for Struts 3:
>>> Rename Struts 2 packages to org.apache.struts
>>>
>>>
>>> Regards
>>> --
>>> Łukasz
>>> + 48 606 323 122 http://www.lenart.org.pl/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Plan for Struts 3
Posted by "info@flyingfischer.ch" <in...@flyingfischer.ch>.
There is a lot of code out there still relying on Java 6.
If there is no urgent need to use Java 7, it is no good idea to make the
framework dependent on Java 7:
We should keep a minimal backward compatibility regarding Java.
Markus Fischer
Am 18.04.2013 08:46, schrieb Johannes Geppert:
> Hi,
>
>> Switch to Java 1.6
> when starting a new major release why not start with Java 7?
> I mean Java 6 is already in the end of life cycle. :-)
>
> Johannes
>
> #################################################
> web: http://www.jgeppert.com
> twitter: http://twitter.com/jogep
>
>
>
> 2013/4/18 Lukasz Lenart <lu...@apache.org>
>
>> A new plan :D
>>
>> Plan for Struts 2.5:
>> Request Git repo from INFRA
>> Import project
>> Remove deprecated plugins
>> Drop support for Struts 1 (remove plugin)
>> Remove deprecated APIs
>> Switch to Java 1.6
>> Rename XWork packages to org.apache.struts.xwork
>> Prepare the first release
>>
>> Plan for Struts 3:
>> Rename Struts 2 packages to org.apache.struts
>>
>>
>> Regards
>> --
>> Łukasz
>> + 48 606 323 122 http://www.lenart.org.pl/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Plan for Struts 3
Posted by Konstantin Priblouda <kp...@yahoo.com>.
Yep, it is. You should go for 1.7 and nobody will have problem with it.
----[ Konstantin Pribluda http://www.pribluda.de ]----------------
JTec quality components: http://www.pribluda.de/projects/
________________________________
From: Johannes Geppert <jo...@apache.org>
To: Struts Developers List <de...@struts.apache.org>
Sent: Thursday, April 18, 2013 8:46 AM
Subject: Re: Plan for Struts 3
Hi,
> Switch to Java 1.6
when starting a new major release why not start with Java 7?
I mean Java 6 is already in the end of life cycle. :-)
Johannes
#################################################
web: http://www.jgeppert.com
twitter: http://twitter.com/jogep
2013/4/18 Lukasz Lenart <lu...@apache.org>
> A new plan :D
>
> Plan for Struts 2.5:
> Request Git repo from INFRA
> Import project
> Remove deprecated plugins
> Drop support for Struts 1 (remove plugin)
> Remove deprecated APIs
> Switch to Java 1.6
> Rename XWork packages to org.apache.struts.xwork
> Prepare the first release
>
> Plan for Struts 3:
> Rename Struts 2 packages to org.apache.struts
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: Plan for Struts 3
Posted by Johannes Geppert <jo...@apache.org>.
Hi,
> Switch to Java 1.6
when starting a new major release why not start with Java 7?
I mean Java 6 is already in the end of life cycle. :-)
Johannes
#################################################
web: http://www.jgeppert.com
twitter: http://twitter.com/jogep
2013/4/18 Lukasz Lenart <lu...@apache.org>
> A new plan :D
>
> Plan for Struts 2.5:
> Request Git repo from INFRA
> Import project
> Remove deprecated plugins
> Drop support for Struts 1 (remove plugin)
> Remove deprecated APIs
> Switch to Java 1.6
> Rename XWork packages to org.apache.struts.xwork
> Prepare the first release
>
> Plan for Struts 3:
> Rename Struts 2 packages to org.apache.struts
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>