Sunday, February 15, 2009

Apache Click 2.0.1 now available

Apache Click 2.0.1 is the first release from the Apache Software Foundation Incubator and is based on the 1.5.1 code base.

Both 1.5.1 and 2.0.1 are considered stable and only bug fixes will be applied to these branches. New development will happen on 2.1.0, the next major version of Apache Click.

For this release we had to make some changes especially around incompatible licensed third-party software. Below is a short summary of these changes. More details and upgrade notes can be found in Roadmap and Changes.

Changes are:
  • Packages were renamed to ''. When upgrading from older releases you will need to convert from '' to ''.
  • DateField used the incompatibly licensed JSCalendar which had to be dropped. Don't worry though, DateField still exists and has been converted to a TextField which understands how to parse and format Date objects. Further a new Click Calendar project was created which is a port of the old DateField functionality. The Click Calendar jar contains a single class called CalendarField which subclasses DateField and has the same API and functionality as the old DateField. When upgrading you can just rename your old DateField to CalendarField to get the popup calendar working.
  • The Chart controls was also using an incompatible licensed JavaScript library and these components was removed. A new project called Click Charts was created for these components. They still use the '' package so no code changes will be necessary.
The next major release will be 2.1.0 and a new feature roadmap is being determined.


The Click team.


Apache Click is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.


florin said...


Thank you so much. Roadmap?

1. I would add form validation with JavaScript generated in the client along with the serverside validation.

2. Wizard mini framework to allow easy multi page form definition and control.

Thank you.

jgbr said...


Thank you for the new release.
I could update the application without any problem. The new ColorPicker does not seem to work properly. So I have to use the old one.

1. Javascript validation at the client should be optional, because low-end mobile phones can not handle javascript properly.

2 Wizard framework is not that important because a such components are rather application specific. But this is only my personal opinion.

Bob Schellink said...

Sorry about not replying here. Blogger wasn't setup to mail me about comments.

About the ColorPicker, we had to remove the old one because of licensing issues. Of course you can still use the old one if needed. However I'd really like to sort out any issues you run into with the new one.

If you have a few spare cycles could you open a JIRA and describe the issues you run into? Is it browser specific stuff?

kind regards