A Wicket Diary

After some hard labour, I’ve finally released the second release candidate of Wicket 1.1. Thank you all for waiting and keeping your fingers crossed. Here are the release notes:

The wicket team is pleased to announce the Wicket 1.1-rc2 release!

http://wicket.sourceforge.net

Wicket is a Java web application framework that takes simplicity, separation
of concerns and ease of development to a whole new level. Wicket pages can be
mocked up, previewed and later revised using standard WYSIWYG HTML design
tools. Dynamic content processing and form handling is all handled in Java
code using a first-class component model backed by POJO data beans that can
easily be persisted using your favourite technology.

Changes in this version include:

New Features:

• added class wicket.markup.html.image.resource.BlobImageResource to make
  working with images from databases easier.
• Made FileResourceStream non-final to support using custom content type
  schemas etc

Fixed bugs:

• Image components inside a border component are resolved by the parent of
  the border, thus keeping pre-viewability and componentization. Issue:
  1312787. Thanks to Ari Suutari.
• Borders now treat autolinked resources within wicket:head tags correctly
  Issue: 1289768. Thanks to Jan Bares.
• skip content of script tag. Treat it as raw markup Issue: 1287640. Thanks
  to Jan Bares.
• Wrong impl. on getParameters() of WebRequestWithCryptedUrl Issue: 1275726.
• Added serialversionuid to all the serialized wicket classes Issue: 1288373.
• Link altered child visibility based on wicket id; hidden ‘feature’ is
  removed now. Issue: 1297446. Thanks to Sven Meier.
• Improved hangman letter images to use just one image reference. Issue:
  1297449. Thanks to Sven Meier.
• doc fix for Button.setDefaultFormProcessing Issue: 1287878. Thanks to Leo
  West.
• Call invalidate after each setXXX invocation on DefaultButtonImageResource
  to force re-rendering Issue: 1266998. Thanks to Johan Compagner.
• Made WicketExampleHeader.html (X)HTML compliant Issue: 1267147. Thanks to
  Jan Bares.
• Link.autoEnable is now false by default, and when setEnabled is called,
  autoEnable will be set to false too as calling setEnabled is a consious
  action that has no effect when autoEnable is true Issue: 1251658. Thanks to
  Zhenbang Wei, Niclas Hedhman.
• Link.autoEnable is now false by default, and when setEnabled is called,
  autoEnable will be set to false too as calling setEnabled is a consious
  action that has no effect when autoEnable is true. Autolinks are
  autoEnabled by default, and so are the paging navigator links. CHECK YOUR
  CODE WHETHER THIS HAS CONSEQUENCES FOR YOU! Issue: 1240768. Thanks to Gili
  Tzabari.
• Models not detached when checkAccess() returns false. Issue: 1290352.
  Thanks to Phil Kulak.
• DatePicker fails when used multiple times in the same page Issue: 1290843.
  Thanks to Ralf Ebert.
• Buttons with empty value are not found as submit button Issue: 1298789.
• Persisted form values not loaded for bookmarkable/redirect pages Issue:
  1298795.
• Moved Dojo and Scriptaculous dependencies out of core into contrib packages
  Issue: 1298082.
• Renamed pageableListViewNavigation field and getter in PagingNavigator
  Issue: 1288863. Thanks to Igor Vaynberg.
• Patch for error in javadoc in ApplicationPages Issue: 1294381. Thanks to
  Igor Vaynberg.
• form now checks on enctype attribute. If the attribute is multipart, the
  multipart property of the form object will be set to that.
• AJAX component doesn’t get correct request parameter path Issue: 1292416.

Changes:

• Add WebPage(PageParameters) constructor (helps with your IDE’s code
  completion features) Issue: 1284625. Thanks to Gwyn Evans.
• made Link.isEnabled non final so that users can more easily customize
  on/off behaviour.

Have fun!
-The wicket team

Having not overcome my problems with the Wicket maven build, I disabled the junit-report and clover report from the project descriptor, and apparently, Maven 1.1-beta-2 can now build the Wicket project distribution. Enabling these reports and running them from the site plugin just works, so I guess it has something to do with the distribution plugin.

Anyhow…. Expect to be able to download the Wicket 1.1-rc2 within the hour!

I don’t think I’m able to create the release of Wicket 1.1-rc2 this evening. I’m having trouble with Maven 1.1-beta2. Everything worked perfectly last build, but somehow I’m not able to run the ‘maven dist’ command in order to produce the Wicket distribution. And the reason I stepped up onto the 1.1 wagon was that my previous maven installation (1.0.2) was busted and has been ever since.

I’ll try running it on my Power mac, and hope I’m finished around 1:30am, otherwise I’m off to bed and have to postpone till tomorrow. I’d hate to arrive at the office with an apple symbol engraved in my forehead.

Note that I don’t complain: it is still beta, and I enjoy using Maven. It probably is something I did wrong in customizing my build. For anyone reading this: this is the error I recieve:

BUILD FAILED
File...... c:\maven-1.1-beta2\cache\maven-xdoc-plugin-1.9.2\plugin.jelly
Element... x:parse
Line...... 122
Column.... -1
Error on line 30381 of document  : Parser has reached the entity expansion limit "64,000" set by the Application. Nested
 exception: Parser has reached the entity expansion limit "64,000" set by the Application.
Total time   : 37 seconds
Finished at  : Wednesday, October 5, 2005 12:36:11 AM CEST

Update: I’ve confirmed this also happens on Mac OSX. Too bad… I’m hoping for some response on the maven mailinglist. I’ll keep everyone informed, and you’ll be the first to know when the release has been baked.