I was noticing that Wicket seems to have a lot of dependencies. I think that is great (because you aren't reinventing the wheel), but it can easily cause great frustration if Wicket is used with other frameworks that require a different version of one or more of those dependencies.
I noticed that Groovy is currently using the below tool (called JarJar) so Groovy can be easily dropped into a project without potential for library version collisions. I haven't used it, but it appears to repackage dependent libraries into the main Jar file with different package names. The main code automatically references the new dependent package names. http://tonicsystems.com/products/jarjar/ The benefits I see: 1) Just one Jar for people to drop into their webapp (I'm always for making things feel easier and cleaner for new uers :-) 2) No strange issues related to dependency conflicts. (Another ease-of-use/lack-of-frustration feature) 3) Fewer posts asking why something doesn't work when it's just a library version issue. My 2 cents :-) Jonathan ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. www.katun.com ********************************************************************** ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
