Neil,
I am afraid you miss the most important argument: whether the core
developer *want* to develop with Java 5. Its mostly their free time and
love they put in Wicket, we should never forget that. (Of course they
probably want to have users, etc. But in the end it is their decision.)
Exactly!
Also those organizations, which want to stay with very old and normally
unsupported software versions usually budget for extra support. Java 1.5
is not supported normally any more by Sun, so they will be bying Sun
retirement support anyway or running all their business systems on
And let's not forget that nobody is suggesting moving current Wicket
versions to Java 1.6. For those poor souls who are stuck developing
for Java 1.5 there is still Wicket 1.4, or even 1.3 for that matter.
The increase in speed alone is reason enough to switch to 1.6 in my opinion.
but isn't that increase of speed only relevant during runtime? imho it doesn't
matter if you compile with 1.5
or 1.6 as long as you run it with 1.6
Regards
Kai
--- Original Nachricht ---
Absender: Jeroen Steenbeeke
Datum: 22.12.2009 12:47
And let's not forget that nobody is suggesting moving
Finished a project at the beginning of the year that was Wicket
based. The designers really loved it, they didn't have much
experience with designing for Java-based frameworks (they hacked ASP/
ASP.NET mostly). I drew up a quick tutorial covering the basics of
Wicket, how to preserve the
We were rocking 1.3.5 btw.
On 22-Dec-09, at 9:30 PM, Craig Tataryn wrote:
Finished a project at the beginning of the year that was Wicket
based. The designers really loved it, they didn't have much
experience with designing for Java-based frameworks (they hacked ASP/
ASP.NET mostly). I
