Logfilter is a tool for performing ad hoc analysis on Apache log files. Logfilter is especially useful when you wish to find records matching very specific criteria, since you can specify exactly which fields to match. The tool also plays well in a Unix environment by accepting input either through files or via stdin.
managelogs is a log processing program to be used in conjunction with Apache's piped logfile feature. It is an alternative to the well known rotatelogs and cronolog programs. Its primary purpose is to solve the "log filesystem full" issue by purging the oldest log files when the total log size exceeds a given value. It can also write compressed files, maintain symbolic links to the current and archive log files, and setuid to a given user. It maintains its state across Apache restarts, and allows writing to several output channels, each one having its own configuration.
The maven-buildmetadata-plugin is a Maven 2 plugin that helps you easily add build metadata to generated archive artifacts. When a product is running on an application server, this tool can tell you which version of which artifact is currently running on that server, which artifact maps to which source code version in the SCM repository, what configuration set (including profiles and environment variables) has been used to generate the artifact, on which machine was the artifact built, and when was the artifact built. The provided metadata include SCM information, build time, operating system, Java runtime, Maven execution information, build user, build host name, and build version.
metagloss is an annotation-centric Android library for reducing boilerplate code. Relying on run-time parsing and compile-time code generation, metagloss provides facilities for mapping XML and databases to data objects, dealing with preference screens and working with DB queries.
mime4j provides a parser, MimeStreamParser, for e-mail message streams in plain RFC822 and MIME format. The parser uses a callback mechanism to report parsing events such as the start of an entity header, the start of a body, etc. If you are familiar with the SAX XML parser interface you should have no problem getting started with mime4j. The parser only deals with the structure of the message stream and won't do any decoding of base64 or quoted-printable encoded header fields and bodies. This is intentional - the parser should only provide the most basic functionality needed to build more complex parsers.