The svnmailer is a tool that is usually called by a subversion hook to submit commit notifications in various ways (at the moment: mail via SMTP or a pipe to a sendmail like program, news via NNTP, or CIA live tracker notification via XML-RPC). It is derived from the original mailer.py distributed with subversion, but should be much more consistent, more extensible, and have many more features.
The mission of the Apache Portable Runtime (APR) project is to create and maintain software libraries that provide a predictable and consistent interface to underlying platform- specific implementations. The primary goal is to provide an API to which software developers may code and be assured of predictable if not identical behaviour regardless of the platform on which their software is built, relieving them of the need to code special-case conditions to work around or take advantage of platform-specific deficiencies or features.
OpenSAML is a portable implementation of the Security Assertion Markup Language (SAML) standard for the formation and exchange of authentication, attribute, and authorization data using XML, as defined by OASIS. There are interfaces for a range of languages, including C++ and Java.
Log4php is a PHP port of Log4j, the most popular Java logging framework. It supports configuration through XML and properties files (with the same structure as log4j) and custom Configurators. File, RollingFile, DailyFile, Echo, Console, Mail, PEAR::Db, PHP error, Syslog or NT events, and socket appenders are supported. Simple, TTCC, Pattern, Html, and Xml Layouts are supported. It also supports Filters, custom Levels, and Loggers. Internal debugging can be switched on and off. Log4php can be used inside a class or inside a main/sub function.
VRaptor 2 is a Web-based MVC and IOC framework based on many frameworks and ideas (Seam, Stripes, Webwork, Hibernate Annotations, etc). It makes full use of Java 5 Annotations. It favors convention over configuration, because configuration in XML/properties/annotations is always easy to make mistakes and repetitive (aka copy and paste in many places). This framework uses a more imperative approach, instead of having many XML files to configure lifecycle and other properties. Most of the settings go inside plain Java objects (POJO), so the team knows exactly what is going on and where.