I'm using the 1.x branch of Wicket (from about 2 weeks ago), and would like to use wicket-contrib-scriptaculous, but from a brief conversation on ##wicket on freenode (where people are infinitely helpful and a real credit to the project), it appears that this is maybe not as easy as perhaps it should be (talk of Maven builds, and undocumented dependencies on particular versions of other libraries).
It was hinted that maybe some people need an excuse to package this stuff so that it is more conveniently accessible, if so, consider this to be just such an excuse :-) Really, if something can be packaged as a simple .jar that you can drop into your project, then it should be - asking people to build it themselves, a process that is not well documented so far as I can see - is not a good option and really doesn't do credit to all of your hard work. Ian. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
