Re: Wicketstuff confluence export

[Kai Grabfelder]

Please also note that some of the links on the main wicket website still point 
to confluence - e.g. the links
on http://wicket.apache.org/learn/projects/authroles.html#alternatives

I guess those should go to githup instead now

--- Original Nachricht ---
Absender: Michael O'Cleirigh
Datum: 11.04.2011 14:59
 Thanks for this Martijn.
 
 I think we should create issues in github for each module to be migrated 
 then hopefully get some volunteers to help out with the migration of 
 content.
 
 I'll see what I can do for this tonight (GMT-4)
 
 Regards,
 
 Mike
 I've exported all confluence WIKI pages to static HTML. You can find it here:

 http://wicketstuff.org/STUFFWIKI/index.html

 I would urge anyone maintaining projects to migrate their content to
 the github wiki.

 Martijn

 
 

Re: wicket 1.5 build is failing because of 1.6 deps...

[Kai Grabfelder]

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 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.
 

Re: wicket 1.5 build is failing because of 1.6 deps...

[Kai Grabfelder]

-1 for requiring JDK 6

We are starting even new projects with JDK 5 (customer requirement - mostly 
large financial or retail
companies). Given the speed of the JDK 1.4  JDK 5 migration they will stick 
with JDK 5 (and IE 6) for at
least the next 3-4 years.

I don't like it either but thats just the way it is in the enterprise business 
;-(

--- Original Nachricht ---
Absender: Johan Compagner
Datum: 15.12.2009 12:42
 i cant believe that..java 6 is already out for years.. they are already at
 update 17..
 java 5 was sep 2004!
 java 6 dec 2006
 
 thats already 3 years ago..
 
 I cant beleive that there are many still on java 5 they really should
 upgrade because java 6 didnt maybe bring much api wise
 but performance wise it was quite a good jump.
 
 Besides that when wicket 1.5 will be released we will be i guess at least
 half next year
 then java 7 is almost there. (i think... java 7 is just a bit question mark)
 
 
 
 On Tue, Dec 15, 2009 at 12:36, Carl-Eric Menzel 
 cm.wic...@users.bitforce.com wrote:
 
 On Tue, 15 Dec 2009 11:44:23 +0100
 Martijn Dashorst martijn.dasho...@gmail.com wrote:

  I was going to propose a vote in that direction... as JDK 1.5 has been
  shelved...
 

 It'll be years until Java 1.6 is as common as 1.5 is now. There are many
 organizations who have only just completed the move to 1.5. I think
 going to a strict requirement for Java 1.6 would be a really bad idea,
 especially since it does not offer as many significant new benefits as
 1.5 did.

 Offering 1.6-specific features in a separate jar would be a simple and
 pretty good solution, I think. Stuff like the typesafe model would thus
 be available for those who need it, without leaving anybody needlessly
 stranded.

 Carl-Eric