Berkano Bookmarks — One of the main ideas behind starting Berkano - still far from mature unfortunately - provides a simple api to manage bookmarks: can be used to form navigation menus, in such a way that they're user customizable, for instance.
Berkano Sample — A couple of demos, samples and a sandbox for Berkano.
Berkano Sandbox — This is a melting pot project that's partly a demo and partly a sandbox for other subprojects. (Berkano User UI for WebWork was born in there, for instance)
Berkano Tools — A bunch of tools or utilities that can be required by other Berkano modules (like Berkano Util), but which are in any case useable and useful outside the context of Berkano.
Berkano Beandisplaytag — A simple taglib to display a bean in a table, à la displaytag, but with one bean instead of a collection, each property being a row instead of a column.
Berkano Kiss Tags — A collection of very simple tags, like drop down boxes of number lists, ...
Berkano TaglibUnit — A small framework based on HttpUnit's ServletUnit to help testing taglibs.
Berkano Util — A handful of util classes: a naïve cache, two hibernate custom types, a template-based mail utility package, an small IO utility api, an url helper for WebWork, ...
Puzzles — Puzzles' aim is to provide an easy way to add functionalities to an application through plugins.
Taskman — A simple task assignement and event-based library
Berkano User . Grouping Page — These modules handle security and user management requirements in j2ee web apps. Enhancements or add-ons to existing security framework, an api for user persistence, password management, and ui components ready to be integrated in your own web apps.
Berkano Seraph — An extension to Atlassian's Seraph, which uses Berkano User for user authentication.
Berkano Seraph Taglib — A collection of simple security-related tags using Atlassian's Seraph and the Berkano Seraph add-on.
Berkano User — A simple user management library. Contains a simple user model and a couple of DAOs, profile and password management components. Current dao implementations are hibernate-based. Should happily replace OSUser.