using 1.5 features to target 1.4 is not very easy. (for example if you also use autoboxing then a under the hood a 1.5 method is called)
I think we have to wait a bit more. Wicket is a server side lib and if there is one place where older jvm's are used then it is the server side...
johan
Eelco Hillenius wrote:
Hmmm... dunno. Is it really worth the effort? It will make it generally harder for people to build the project, as not everyone will have JDK1.5 installed.
You want this in 1.0?
Eelco
Jonathan Locke wrote:
if we are all nice and backwards compatible in a binary sense, it might be nice to use generics in some places. in particular the listenerset class i'm working on would be better implemented that way.
what do we think about generifying code and requiring 1.5 to build the core?
jon
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
