Taken from the Wicket mailing list:
> Hey folks, The Basement Coders will be at JavaOne and doing
> a podcast right http://www.phpaide.com/?langue=fr&id=16 from the Mason street tent Tuesday at
> 10am! We would love to meet some Wicket peeps
> throughout the week!
As Wicket Security will not be adopted into core, we’ll be changing
the package name and project name going forward. We’re still not sure
about the final name, but these two are the runners up:
Both are nice names, and both have their pros and cons. Let us know
which one you prefer.
Furthermore we’ll be adding new annotations such that you’ll be able
to authorize your pages using a Java class (for the principal) and an
annotation on your page to specify which principals are required. This
will eliminate the need for the policy files.
These changes will come in the first 1.5 milestone release.
- Support for Wicket 1.5
- A new home
- Deployment to maven central instead of wicketstuff repo
We expect to release the first milestone in a week or so. The final 1.5 release will occur some time after Wicket 1.5 has been finalized.
The Wicket Security project WASP/SWARM has released a new version: 1.4.1
News worthy changes:
- Moved code from SwarmStrategy to AbstractSwarmStrategy to allow reuse with different implementations
- Logout now uses Session.invalidate() instead of invalidateNow(), to prevent problems with the request logger
- Spring example is now based on Spring 3
- Wicket dependency upgraded to 1.4.12
You can download the release from the Wicket stuff repository:
Or upgrade using the following in your pom: