Download JAR files tagged by using with all dependencies

Skin Look And Feel allows Java developers to write skin-able application using the Swing toolkit. Skin Look And Feel is able to load themepacks (a bundle of GTK - The Gimp Toolkit - and KDE - The K Desktop Environment - skins) to enhance your application GUI controls such as Buttons, Checks, Radios, Scrollbars, Progress Bar, Lists, Tables, Internal Frames, Colors, Background Textures, Regular Windows. Skin Look And Feel (aka SkinLF) also includes NativeSkin to create irregular windows.

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 favorite technology.

SableCC is an object-oriented framework that generates compilers (and interpreters) in the Java programming language. This framework is based on two fundamental design decisions. Firstly, the framework uses object-oriented techniques to automatically build a strictly-typed abstract syntax tree. Secondly, the framework generates tree-walker classes using an extended version of the visitor design pattern which enables the implementation of actions on the nodes of the abstract syntax tree using inheritance. These two design decisions lead to a tool that supports a shorter development cycle for constructing compilers.

Stopwatch is a free, simple, highly extensible, Java API that allows developers to easily monitor whole application or any part of it. By default Stopwatch generate reports about hits, execution times (total, average, minimum, maximum) as well as load but it can be easily extended to measure anything else by providing custom engine. Out of the box Stopwatch uses an in-memory HSQL database. It is able to persist collected data using a "storage". There is "storage" provided to persist into HSQL database and custom "storage" can be easily integrated.

NekoDTD is a configuration that parses Document Type Definition (DTD) files and converts the information into an XML document. This representation can then be processed using standard XML processors and applications to perform grammar analysis, convert the DTD into other grammar formats, etc. For example, using an XSLT stylesheet, the XML representation of the DTD can be converted to an equivalent XML Schema or Relax NG grammar. The NekoDTD parser configuration is written using the Xerces Native Interface (XNI) that is the foundation of the Xerces2 implementation. This enables you to use NekoDTD with existing XNI tools without modification or rewriting code.

A tool to help visualise API differences between two different versions of a project. Jardiff takes two jar files and outputs all the public API changes as xml, html or plain text. Currently this is command line driven, though we are working on an ant plugin. It requires java 1.4 to run. <h2>Background</h2> At OSjava, we were using a shell script to work out API differences between our release versions. This unfortunately doesn't scale very well to larger projects, the main reason for jardiff was to do the same in a much shorter time (From memory it was taking minutes to get the API diff from two fairly small jars). In it's current state, jardiff can generate the api differences between rt.jar for java 1.4 and java 1.5 in under 20 seconds, so it should scale to even the largest of projects.

How many classes does it take to make a cache? 60? 80? You might think so if you look at the other caches on the market. Ashkay is a streamlined, simple cache that in many ways is more powerful than the other mainstream caches. Ashkay is a strategy based caching tool. In most cases, you might be using a configuration file to tell the cache what rules it should obey. Or, you might just be setting properties on the cache. I have never liked this model as it limits me, the user of the cache to strategies the developer decided were important. Instead, Ashkay lets you choose the strategy(ies) to use when caching certain objects. Of course, a few of the most handy strategies are pre-packaged, but implementing a new one is a simple as can be. Ashkay is a fork of <a href="http://xot.sf.net">xot</a> caching code. Made more sense on its own.