2013/4/18 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. :-)
Good question :-) But I think there are users which migrated to Java 6
already and they don't have a plans to migrate t
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,
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
To: Struts Developers List
Sent:
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
> A
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
