SpiderDB is a lightweight database schema crawler library developed using Java. It is a simple library that can be used to Crawler the underlying schema of a database and return POJO objects, which makes it very easy to use. This library takes care of all the differences among the various database management systems, and makes application code free from the DBMS differences.You keep using same POJOs even if you change the underlying DBMS.
nioReactor is a framework for quickly building scalable event-driven network applications. It is built on top of the Reactor design pattern using NIO sockets. This provides high performance and allows for a complete separation from the application specific code. The goal of the project is to provide a simple set of APIs that allow users to build scalable servers without needing to deal with with the cumbersome and sometimes temperamental peaces of the NIO package.
persistence4j is a small and lightweight Java object persister that uses JDBC to persist data into a relational database. The library frees you from writing the Data transfer objects - just create a POJO and simply save it. Transactional and non-transactional connections are supported and can be configured from the simple properties file.
MSBLayout is a layout manager for Java AWT and Swing that combines the nested-boxes approach of BoxLayout with flexible constraints as used by GridBagLayout. A concise API with good defaults minimizes the code required to get the layout you want. MSBLayout makes it easy to align and justify components and to synchronize their sizes. Gaps between components can be inserted automatically. Optimized resizing behaviour keeps your dialogs looking good when displayed larger or smaller than their preferred sizes. The API is also well suited for constructing layouts dynamically at run-time.
UnitTH is a lightweight application for generating a comprehensive HTML test history report out of a set of parsed JUnit XML test reports. The historical report collects all JUnit reports and makes it easy to navigate between them. In addition, the report contains a large number of sortable test statistics for test runs, individual test modules, and test cases. A number of graphs are generated and useful trends can very easily be spotted. There are two intended usages for UnitTH. First, it can be useful for unstable and sporadically failing test suites, for which it might sometimes be necessary to run the suite multiple times to be able to make a solid judgment regarding the outcome of the test runs. Second, it can be used for test history reporting in continuous integration like projects.