Trying to write all of the announcements and make sure all the documentation on the site is reasonably up-to-date is also a critical part of any release. And it takes a long time. We were all scrambling to try to get it done.
-- Jeremy Thomerson http://www.wickettraining.com On Fri, Jul 31, 2009 at 8:55 AM, Craig McIlwee<[email protected]> wrote: > I heard someone saying here a few weeks ago that the 1.4.0 build had been > finalized and that the official release was waiting on some PR stuff. Just > curious what that was? > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Martijn Dashorst > Sent: Thursday, July 30, 2009 6:54 AM > To: > [email protected];[email protected];[email protected];[email protected] > Subject: Apache Wicket 1.4 takes type safety to the next level > > The Apache Wicket project is proud to announce the release of Apache > Wicket 1.4. Apache Wicket is an open source, component oriented Java > web application framework. With overwhelming support from the user > community, this release marks a departure from the past where we leave > Java 1.4 behind and we require Java 5 as the minimum JDK version. By > moving to Java 5 as the required minimum platform, we were able to > utilize Java 5 idioms and increase the type safety of our APIs. Using > Java generics you can now write typesafe web applications and create > typesafe, self documenting, reusable custom components. > > The full announcement for this release can be found here: > http://wicket.apache.org/apache-wicket-14-takes-type-safety-to-the-next-level.html > > Download Apache Wicket 1.4 > > You can download the release here: > http://www.apache.org/dyn/closer.cgi/wicket/1.4.0 > > Or use this in your Maven pom's to upgrade to the new version: > > <dependency> > <groupId>org.apache.wicket</groupId> > <artifactId>wicket</artifactId> > <version>1.4.0</version> > </dependency> > > You will need to upgrade all modules (i.e. wicket, wicket-extensions) > to their 1.4 counterparts. It is not possible to mix Wicket 1.3 > libraries with 1.4 libraries due to API changes. > > Most notable changes > > From all the changes that went into this release, the following are > the most important ones: > > * Generified IModel interface and implementations increases type > safety in your Wicket applications > * Component#getModel() and Component#setModel() have been renamed to > getDefaultModel() and setDefaultModel() to better support generified > models > * The Spring modules have been merged (wicket-spring-annot is now > obsolete, all you need is wicket-spring) > * Many API's have been altered to better work with Java 5's idioms > * Wicket jars are now packaged with metadata that makes them OSGI bundles > > Apart from these changes, the release is mostly compatible with Wicket > 1.3 and upgrading shouldn't take too long. Early adopters report about > a days work to upgrade medium to large applications to Wicket 1.4. > Read the migration guide to learn more about the changes in our APIs. > To learn more about all the improvements and new features that went > into this release, check the solved issue list in our JIRA instance. > > If you want to learn more about this release, please refer to the full > release announcement: > http://wicket.apache.org/apache-wicket-14-takes-type-safety-to-the-next-level.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
